Well, I've made that change in the app, however we got a 108 error this morning. I was doubtful that this was really the problem because after reopening the app, the problem did not go away. What are the chances that there is another conflict on the second attempt? And, as I mentioned in the original post, the behavior is suggestive of a low memory problem.

The error log reports that the error is occurring in the itableform.dataenvironment.OpenTables method at line zero. I decided to go ahead with setting TABLEVALIDATE to 7 and scale back from there if I saw problems during a save, but since this is at the point the form is loading, it's not a conflict during a save, so moving to 5 would probably not help.

Thanks for your input on this. Any additional thoughts would be appreciated.

Russell