Hello,
I have a database where users have locally installed a 2007 or 2010 front-end (FE). The back-end (BE) is on a file-server accessible by all users.
Unfortunately the network connection is not always the best, resulting in possible interruptions during a write operation.
Which then causes the record in the BE to get corrupted.
As a result I need to go back to the last saved backup and restore the record.
To make things worse, the main table uses an auto number field which logically does not allow me to restore the record with the previous used auto number.
Resulting in the item getting a new ID number.
Also the BE is only 2MB big, but it takes long to open up.
Question:
- What options (VBA, FE/BE design) do I have to make the BE less vulnerable to corruption in a slow network environment?
- What options do I have to make the FE/BE database faster?
Thanks
Tim
I have a database where users have locally installed a 2007 or 2010 front-end (FE). The back-end (BE) is on a file-server accessible by all users.
Unfortunately the network connection is not always the best, resulting in possible interruptions during a write operation.
Which then causes the record in the BE to get corrupted.
As a result I need to go back to the last saved backup and restore the record.
To make things worse, the main table uses an auto number field which logically does not allow me to restore the record with the previous used auto number.
Resulting in the item getting a new ID number.
Also the BE is only 2MB big, but it takes long to open up.
Question:
- What options (VBA, FE/BE design) do I have to make the BE less vulnerable to corruption in a slow network environment?
- What options do I have to make the FE/BE database faster?
Thanks
Tim