Datasheet Form Mysteriously Crashes

[reeves311]

I have a simple run-time database. From the main menu, user's click a button with an openform macro to open a form in datasheet view. This form has a custom built shortcut menu with sorting and filtering options on it which works well. The problem is, the form will work for several days with multiple users using the form simultaneously, then it freezes. When it freezes, you can click the button on the main menu to open it, but nothing happens. After this happens, if I open the database in accdb mode and double-click the form in the navigation pane, it won't open, it does nothing. However, if I open it in design view, then click View in the upper left hand corner, it opens in datasheet view just fine. But back to double-clicking it in the navigation pane and it still won't open. This goes on for a while, then suddenly it works again and I have no idea why it suddenly works. I am not a programmer so this is a simple form built in graphic mode. I have tried compacting and repairing the database, and it changes nothing. I have tried rebuilding the form from scratch and the same thing happens. I thought perhaps it had something to do with the filteronload or orderbyonload and have turned those options off. Any clue what's going on? I have built these simple forms 100 times and never had this problem before. I would appreciate any help I can get. I have searched google for hours with no results.

[Missinglinq]

My guess is that this app hasn't been split into a Front End/Back End configuration. If this assumption is accurate, you should know that having multiple users sharing a single, non-split database, sitting on a network drive is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior, including the problem you're having, now! Multiple users simply have to work off of a split database, with each user having their own copy of the Front End, which contains everything except the data/tables, on their respective hard drives, and a Back End with only the Tables on a shared drive.

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past seven years have seen dozens and dozens of reports of non-split apps causing these kinds of problems as well as data loss! The really insidious thing is that a non-split app can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

The record, by the way, was a Non-Split db that had been working, without problems, for 12 years! It then started exhibiting all of the symptoms listed above and continued to do so until the app was split.

If data-loss isn't important, and the app being down won't cost you production time loss, then by all means leave it non-split.

Splitting an Access database isn't as scary as it sounds; Access will do most of the heavy-lifting for you! Here’s a tutorial on Splitting a Database:

http://www.hitechcoach.com/index.php...atid=24:design

If your app is already split, with the Back End (with all Tables) residing on a shared drive, and a copy of the Front End (with everything except the Tables) residing on each user's PC, let us know.

Linq ;0)>

[reeves311]

I will try this and let you know. Thanks!