Playing with a small network (two computers) while doing side by side comparisons to find problems before putting the database into general use. The forms all have a SAVE button to save and an EXIT button which saves and exits. When more than one user accesses the same database, at the same field, we are not seeing a notice telling the other users that a field is being updated. Example:
1. ID info for Bozo says he has "red hair and very large feet" in a DB Memo field. This comes up on both comps at startup. 2. User 1 adds "He has a very large nose." and saves the info. 3. The screen info on User 2 does not refresh with this new info because Auto refresh defaults at 0. 4. User 2 saves after making edits on other fields on the same form, not knowing there have been changes by User 1 to the DB Memo field on another computer. 5. Checking the table shows that original message and the nose message added by User 1 was overwritten by the message from User 2's screen that did not include the nose message because User 2 saved second. 6. When auto refresh is set at anything but 0, changes made before the refresh are lost unless you are real quick with saving. What is the correct method of notifying multiple users who are updating/editing the same fields so simultaneous changes are shared and not lost? Is there a "best" autorefresh figure? Drop downs and other fields seem to work well. Several other forms have large text fields where concurrency and autorefresh can be a huge problem. Of course all the forms works great in single mode. Using V8 with the 60630 updates on both comps. Tom Frederick Elm City Center 1314 W Walnut Jacksonville, IL 62650 Off - 217-245-9504 Fax - 217-245-2350 Email - [EMAIL PROTECTED] Web - www.elmcity.org
