Lord_Vader
Registered User.
- Local time
- Today, 08:14
- Joined
- Mar 24, 2009
- Messages
- 15
This might sound ridiculous but this is all I can think of.
[PREFACE]
I have a split database, Front end Local, Backend on a LAN. Half our group is on west US, the other on the East. The LAN is out west, so the database runs great out there, out east - not so much.
I've tried getting an SQL server, no luck. So I'm stuck using Access (We have sharepoint, but that speed was terrible for everyone)
I've optimized with all the speed tips I could find, but it's just too slow and so the database is essentially unusable.
[ISSUE]
This is barely a multiuser database. It would be very rare that more than one person would be using it (7 possible) at a time, but rare is still sometimes.
The LAN speed is decentley fast for normal file copy operations so I'm thinking of copying the back end database to the local machine, setting up some sort of lock on the LAN backend. Then overwriting the LAN copy with the changed local copy.
Is this crazy? Anyone have any ideas how I can lock the backend so that if a second user tries to open the front end it will warn them that its read only and they can't make changes?
I have a config file - I guess I could write a line to that saying the database is in use and just have a check whenever the front end is opened? Doesn't seem terribly secure, but it's the best I've got.
[PREFACE]
I have a split database, Front end Local, Backend on a LAN. Half our group is on west US, the other on the East. The LAN is out west, so the database runs great out there, out east - not so much.
I've tried getting an SQL server, no luck. So I'm stuck using Access (We have sharepoint, but that speed was terrible for everyone)
I've optimized with all the speed tips I could find, but it's just too slow and so the database is essentially unusable.
[ISSUE]
This is barely a multiuser database. It would be very rare that more than one person would be using it (7 possible) at a time, but rare is still sometimes.
The LAN speed is decentley fast for normal file copy operations so I'm thinking of copying the back end database to the local machine, setting up some sort of lock on the LAN backend. Then overwriting the LAN copy with the changed local copy.
Is this crazy? Anyone have any ideas how I can lock the backend so that if a second user tries to open the front end it will warn them that its read only and they can't make changes?
I have a config file - I guess I could write a line to that saying the database is in use and just have a check whenever the front end is opened? Doesn't seem terribly secure, but it's the best I've got.
