hello,
I am currently running a database using access 2007. The database is only used on two computers, and the access file (the whole database) is stored on a server. The database us accessed simply by opening it from a shared doc location. In other words the database is not split. I plan to split the database, but it is in the very early stages of operation.
We are using the database to store manufacturing data. The data is entered on the factory floor regularly during the course of a day.
As with any start-up database, there are changes that need to be made. I would like to be able to work on the database (design, and debug) from one computer while the database is still in operation on the factory floor.
How would the database professionals on here (i'm a rookie) handle this situation?
Thanks
I am currently running a database using access 2007. The database is only used on two computers, and the access file (the whole database) is stored on a server. The database us accessed simply by opening it from a shared doc location. In other words the database is not split. I plan to split the database, but it is in the very early stages of operation.
We are using the database to store manufacturing data. The data is entered on the factory floor regularly during the course of a day.
As with any start-up database, there are changes that need to be made. I would like to be able to work on the database (design, and debug) from one computer while the database is still in operation on the factory floor.
How would the database professionals on here (i'm a rookie) handle this situation?
Thanks