Front End on Network
- Thread starter KeithG
- Start date
Plenty.
When you query a SQL server, it does the query on server side. With Access, it asks for whole recordset then does query on client side. In other words, you are tossing forth and back *whole* database across the network. Good way to tax the routers and cables, no?
This also gives you a big performance hit. When I implement my FE, I make sure that all lookup tables are local to the FE to help with the performance otherwise I would be hanged high and dry for forcing my user to wait 10 seconds or more to open a combobox's list
and if that's not enough, you are increasing the risk of data corruption. If you're swapping a recordset and somehow connection dropped... what gets saved? Maybe some. Maybe not. Maybe worse. I don't want to know!
Lastly, how are you going to ensure that your user don't accidentally same same FE? That would create same problem as above.
So, if you really like database recovery, go ahead and put it on network.
When you query a SQL server, it does the query on server side. With Access, it asks for whole recordset then does query on client side. In other words, you are tossing forth and back *whole* database across the network. Good way to tax the routers and cables, no?
This also gives you a big performance hit. When I implement my FE, I make sure that all lookup tables are local to the FE to help with the performance otherwise I would be hanged high and dry for forcing my user to wait 10 seconds or more to open a combobox's list
and if that's not enough, you are increasing the risk of data corruption. If you're swapping a recordset and somehow connection dropped... what gets saved? Maybe some. Maybe not. Maybe worse. I don't want to know!
Lastly, how are you going to ensure that your user don't accidentally same same FE? That would create same problem as above.
So, if you really like database recovery, go ahead and put it on network.
KeithG
AWF VIP
- Local time
- Today, 09:28
- Joined
- Mar 23, 2006
- Messages
- 2,592
Thanks for the reply. I do have all the constent data in local tables. My boss dosen't like the idea of everyone copying the FE to the local machine and I wanted to get some other peoples opion on the subject. How many users access your FE at once?
But hey,
someone posted a sample where you can do automatic updating of FE. That'll alleviate the problem (I think?)
Cruise on over there...
someone posted a sample where you can do automatic updating of FE. That'll alleviate the problem (I think?)
Cruise on over there...
KeithG
AWF VIP
- Local time
- Today, 09:28
- Joined
- Mar 23, 2006
- Messages
- 2,592
Well I designed a database to copy the FE to the users Pc but what my manger is concerned about is the every quarter the IT department will search your computer for .mdb or .mde files and you will have to fill out a 4 page survery on each file they find. I was thinking to avoid this I could tell the users to run the database through winzip and zip the file. But I don't think the IT department would like that too much if they found out. How many users do you have using your FE at once?
If its important to the company workings, then how about talking to the IT department and asking them to raise an exception for the db you are creating? It wouldn't be too hard... they do their scan, and if the name is 'ImportantDB.mde' they don't get you to fill out the survey 
Workmad's is a good solution, especially if you can speak to someone with authority on the IT side. Other thoughts: Consider pilot testing -- put a client file on the server and let two or three users access it. If it goes well for a month, add users incrementally until you're satisfied things are stable. Or you can rename the Access files, changing their extensions so the IT goons miss them...Access can read Access files, regardless of their file name extension.
Regards,
Tim
Regards,
Tim
Similar threads
