rraehal
05-04-2010, 05:19 PM
We use an Oracle application for our primary business needs. Someone at our corporate office wrote an access program that connects to the oracle database and downloads a bunch of data. The access program can then be used to manipulate the data for specific needs.
The access database used an oracle ODBC connection to get the updated information. We only have one server set up to use ODBC so we placed the database there. When you open the database from inside the office it works very well. 30-45 seconds to open the database. Trying to open the database outside the office does not work very well. It takes 10 minutes or more to open the database. If the database is closed before it fully opens (using task manager to kill access) we get a corrupt database that can not be used in our out of the office.
At the moment the access database is fairly empty. it still only has test data. I expect the delay to get longer as more information needs to be sent to remote users.
I do not have any experience using access outside of it being a local file.
How do you recommend i set up my users to be able to sue this file in and out of the office without such a detrimental performance hit.
The server is Windows 2000. The clients are Windows XP and will soon become Windows 7. Access is version 2002. The corporate office does not plan to upgrade to Office 2007 or 2010 at this time.
The access database used an oracle ODBC connection to get the updated information. We only have one server set up to use ODBC so we placed the database there. When you open the database from inside the office it works very well. 30-45 seconds to open the database. Trying to open the database outside the office does not work very well. It takes 10 minutes or more to open the database. If the database is closed before it fully opens (using task manager to kill access) we get a corrupt database that can not be used in our out of the office.
At the moment the access database is fairly empty. it still only has test data. I expect the delay to get longer as more information needs to be sent to remote users.
I do not have any experience using access outside of it being a local file.
How do you recommend i set up my users to be able to sue this file in and out of the office without such a detrimental performance hit.
The server is Windows 2000. The clients are Windows XP and will soon become Windows 7. Access is version 2002. The corporate office does not plan to upgrade to Office 2007 or 2010 at this time.