We have an Access 2010 database that is accessed by some users from another location. Each user has their own copy of the front end. For some reason two users in our Sydney office enter orders, but after they have entered and saved the order, sometimes for no apparent reason they get an "invalid argument" error message and all the data in the order has been converted to hieroglyphics. I cannot seem replicate this from my server location. Can anyone give me some advice on how to determine what might cause this? It seems to only occur from our Sydney based server. Could it be that each user's copy of the front end is located on the same virtual drive on our Melbourne based server? Should I move the Sydney user's copies of the front end to the Sydney based server? I am not sure what to do? I think it might be the growing size of the database but I compacting doesn't reduce it by much. Any help would be appreciated.
Invalid argument and database size
- Thread starter jom1918
- Start date
- Local time
- Today, 05:11
- Joined
- Sep 12, 2006
- Messages
- 16,094
The manifested error sounds like corruption, and as Galaxiom says is a problem of using a WAN, (and often a non-wired network). Be careful, as serious corruption could damage the dbs irretrievably. Make sure you have adequate backups.
managing a distributed database can get complex, and costly.
Adding a terminal server means setting up a new PC to host connected sessions. Your users run apps on your TS, rather than on their own. The TS will need setting up and licensing. You need to be careful to restrict access from unauthorised sources. You need to consider how to make local resources (ie the Sydney printers) available to the (Melbourne) server.
You will surely need some assistance from whoever manages your networks to achieve this
The other way is to treat the Sydney app as freestanding, and then find a way of consolidating this into the Melbourne app, (if necessary) which also adds some complexity.
You need to have a think about what you want/need to achieve.
managing a distributed database can get complex, and costly.
Adding a terminal server means setting up a new PC to host connected sessions. Your users run apps on your TS, rather than on their own. The TS will need setting up and licensing. You need to be careful to restrict access from unauthorised sources. You need to consider how to make local resources (ie the Sydney printers) available to the (Melbourne) server.
You will surely need some assistance from whoever manages your networks to achieve this
The other way is to treat the Sydney app as freestanding, and then find a way of consolidating this into the Melbourne app, (if necessary) which also adds some complexity.
You need to have a think about what you want/need to achieve.
