DoCmd.RunCommand acCmdRefresh 
Author Message
 DoCmd.RunCommand acCmdRefresh

We have a situation where when working with attached SQL Server 6.5 tables
(Service Pack 3) with our Access 97 applications we often receive the "Data
has changed.  Operation stopped..." message if a user changes a record a few
seconds after having updated that record.  We can prevent this message from
occurring using either one of the following methods.  First method: execute
the command DoCmd.RunCommand acCmdRefresh in the AfterUpdate event of the
form that contains the updated record.  Second Method: change the ODBC
Refresh Interval to a very low number, such as 1 second.  Neither one of
these methods is Microsoft's recommended solution as per their Knowledge
Base articles; their solutions do not always work.  I can think of potential
overhead problems if we implement our second method but I can not think of
any overwhelming problems with our first method.  Can anyone think of
potential problems if we use the DoCmd.RunCommand solution?

Thanks for your thoughts,
   Phil Singer



Sat, 03 Jun 2000 03:00:00 GMT  
 DoCmd.RunCommand acCmdRefresh

Why not implement a recordlocking strategy. If records are locked when
edited you do not run into this problem.
The recordlocking can be set from a forms .recordlock property.
--
regards



Sat, 03 Jun 2000 03:00:00 GMT  
 DoCmd.RunCommand acCmdRefresh

Thanks for the reply.  Unfortunately with Access you can not really lock
one, and only one, record at a time.  The choices are to lock all the
records in a table or a "page" of records when one record is being edited.
Neither of those choices is viable for our application.  We have situations
where multiple users may be accessing and updating records in the same table
at the same time and we could make their lives miserable (not to mention our
support staff) implementing any of the Access forms lock strategies.

   Thanks Again,
      Phil


Quote:
>Why not implement a recordlocking strategy. If records are locked when
>edited you do not run into this problem.
>The recordlocking can be set from a forms .recordlock property.
>--
>regards




Sun, 04 Jun 2000 03:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. DoCmd.RunCommand acCmdSaveRecord DoCmd.RunCommand acCmdSaveRecord

2. Docmd. save OR docmd.runcommand acSave

3. docmd.save VS docmd.runcommand acsave???

4. DoCmd.RunCommand acCmdImport

5. DoCmd.RunCommand acCmdFind Help

6. Differences between Me.Undo and DoCmd.RunCommand (acCmdUndo)

7. Calling DoCmd.RunCommand acCmdSaveRecord, after calling an API function

8. docmd.runcommand?

9. Error with DoCmd.RunCommand acCmdSave

10. DoCmd.RunCommand spell check question


 
Powered by phpBB® Forum Software © phpBB Group