You can have up to 32 indexes on a table (I believe that's the limit) so that's not your issue.
If your form is BOUND (i.e. the controls all have a value in the ControlSource property) then you should let Access handle the updates for you. Access bound forms will automatically save data to the underlying table whenever a user moves off the record, closes the form, clicks the Save menuitem etc etc. Using SQL in conjunction with Bound forms can definitely cause issues, the most common of which is a Write Conflict error message.
Corruption happens for many reasons - have you imported the DATA to a new, blank database, and used that one for the backend? The issue isn't with the FE in this case, it's with the Backend ... so if you haven't, do so immediately
Does the db always corrupt on the SAME record? If so, you may need to delete that record and re-create it.
What sort of network are you on? If this is a typical office LAN - that is, a WIRED ethernet system, 100 mbps - then I'd check hardware, cables, nics, routers etc to insure that you don't have a troublesome part. Dropped network connections are one of the most common causes of db corruption.
If you're running this across a wireless network or a VPN/WAN, then you'll continue to experience corruption. Access is a file-server type database, and doesn't work well in those environments.
What opertaing system is used on the machine that houses the backend?
Main Topics
Browse All Topics
by: ShockUKPosted on 2009-08-12 at 05:24:24ID: 25077923
If it causes an problems I do have 2 indexes setup on the table, does anyone think taking them off will sort it out? also a primary key field assigned to an autonumber