merce33
Active Member
- Joined
- Oct 27, 2006
- Messages
- 277
I need help.
The manager of the IT department at our company's headquarters up in the United States told me yesterday I am no longer allowed to use access for anything that will be on the server, LAN, internet or intranet. If I use Access, I can only use it on my desktop and it cannot be attached or linked in any way to the network.
He quoted the following reasons:
1. Access can not operate with multiple users at the same time because of record-locking problems.
2. Access takes up too much room on the server and will run too slow.
Here's the thing:
I work in the Quality department of our manufacturing facility in the Dominican Republic. We have 1400 employees here in DR, but no software or programming support. None. we have to go to corporate in the US for that, but it takes months for a project to even get to the top of their to-do list.
So i invested the time to learn access to try and help out the quality department, i did some small databases (all tables less than 5,000 records), they function well -- no problems with record locking -- and everyone uses & likes them. Everyone's happy right?
So that brings us to yesterday when IT in the states heard about the vicious acts i was committing and told me to stop, and that all database development must go through them.
******************
Sorry about the sob-story. Here is my question to the forum:
Is there any data at all that I can gather which will show that a small Access database, used by only 5 or 6 people simultaneously will not incurr any significant performance hits on our network? Or that there is a certain number of simultaneous users under which Access won't have problems? My databases have been used by 3 people at the same time and we haven't noticed any problems.
The thing is, before I had heard of Microsoft Access several months ago, i was doing very similar things on the network with Excel shared-files and VBA. It was a hassle & really inefficient but they I didn't hear so much as a peep from anyone. Now i switch to access instead of excel and i catch hell from the corporate IT manager.
It's a shame, cause i was starting to like Access....
Thanks,
Mike
The manager of the IT department at our company's headquarters up in the United States told me yesterday I am no longer allowed to use access for anything that will be on the server, LAN, internet or intranet. If I use Access, I can only use it on my desktop and it cannot be attached or linked in any way to the network.
He quoted the following reasons:
1. Access can not operate with multiple users at the same time because of record-locking problems.
2. Access takes up too much room on the server and will run too slow.
Here's the thing:
I work in the Quality department of our manufacturing facility in the Dominican Republic. We have 1400 employees here in DR, but no software or programming support. None. we have to go to corporate in the US for that, but it takes months for a project to even get to the top of their to-do list.
So i invested the time to learn access to try and help out the quality department, i did some small databases (all tables less than 5,000 records), they function well -- no problems with record locking -- and everyone uses & likes them. Everyone's happy right?
So that brings us to yesterday when IT in the states heard about the vicious acts i was committing and told me to stop, and that all database development must go through them.
******************
Sorry about the sob-story. Here is my question to the forum:
Is there any data at all that I can gather which will show that a small Access database, used by only 5 or 6 people simultaneously will not incurr any significant performance hits on our network? Or that there is a certain number of simultaneous users under which Access won't have problems? My databases have been used by 3 people at the same time and we haven't noticed any problems.
The thing is, before I had heard of Microsoft Access several months ago, i was doing very similar things on the network with Excel shared-files and VBA. It was a hassle & really inefficient but they I didn't hear so much as a peep from anyone. Now i switch to access instead of excel and i catch hell from the corporate IT manager.
It's a shame, cause i was starting to like Access....
Thanks,
Mike