We have a form that is not firing the AfterUpdate event, nor is it sending
the resync command to SQL Server.  Does anyone know what could cause this?

We have many forms that function using the same mechanisms, and they both
fire AfterUpdate and send the resync command, as witnessed through SQL
profiler.

Thanks.

Joel

SQL2K, Office2k SR1

How did you create the link between the Form and the event procedure?

I have noticed before that when I create the event procedure in the VBA
editor that a link is not always established. When I edit the form's
properties in the form designer the After Update property is blank rather
than [Event Procedure]. When I click on the ... button then code builder
then it creates the link and fills in [Event Procedure].

Hardy

Quite so, Hardy, and thanks for your response.  I too was aware of this
long-standing Access 'feature', but I did not remember it this time until
just before reading your post.  That was indeed the problem with the
AfterUpdate event.

However, the ResyncCommand still is not getting sent to SQL Server.  If I
modify a record, SQL Profiler reveals that the UPDATE command is sent to
update the record in the database, but it is not followed by the command
contained in the ResyncCommand property.  Other forms doing the same thing
send two commands, first the UPDATE, then the resync.

I have created a new form from scratch, and it has the same problem.  I
tried several different SQL strings as ResyncCommand, and tried setting the
property both in the property pages at design time and from code at runtime.

Ideas anyone?

TIA

Joel

A little more info...

Here's exactly what is happening in Profiler:

The forms that do not work send the following commands after a record has
been updated.

    SET ROWCOUNT 0
    <update command>

A form that does work issues the following commands:

    SET NO_BROWSETABLE ON
    <update command>
    <resync command>
    SET NO_BROWSETABLE OFF

Can anyone help?

Thanks,

Joel