I am posting this question in multiple forums due to the various issues involved. I am looking for any experiences and or suggestions to help me make decisions.
I currently have an Acess mdb for document control in our engineering group running at 2 different sites. One in PA and one in AZ.
Architecture:
-The 2 sites have NT networks and are now connected via T1
-We have a citrix server running at the AZ location to support the companies main business operating software. This could be used.
Goals
-I want to combine the tables of the 2 separate databases, and begin to run out of a common database.
-I would like to stick with access if I can.
-Primary administration will be done from PA.
Basic Info:
-The usage of this database is relatively low.
-It is only edited for a few minutes at a time usually by a handful of users.
-Another 10 or so users may acces it read only 15 minutes a day or so.
- Current size of front end is about 1 meg.
- Current size of back end is 800K in PA and 500K in AZ
- I estimate back end size to grow steadily at about 1-2 meg per year.
The main questions I have at this point are:
1 Where to store the Tables ?
2 THe database contains OLE links to CAD drawings The Cad drawings will be stored on networks at both sites. Should I / can I create some sort of local table to store these links.
3 What is the best method of combining the tables where an autonumber PK field is used as a foreign key in relationships without disrupting the relationship.
4 Should I run the database on the AZ server and utilize the Citrix server.
Dave
gallagherd@earthlink.net
I currently have an Acess mdb for document control in our engineering group running at 2 different sites. One in PA and one in AZ.
Architecture:
-The 2 sites have NT networks and are now connected via T1
-We have a citrix server running at the AZ location to support the companies main business operating software. This could be used.
Goals
-I want to combine the tables of the 2 separate databases, and begin to run out of a common database.
-I would like to stick with access if I can.
-Primary administration will be done from PA.
Basic Info:
-The usage of this database is relatively low.
-It is only edited for a few minutes at a time usually by a handful of users.
-Another 10 or so users may acces it read only 15 minutes a day or so.
- Current size of front end is about 1 meg.
- Current size of back end is 800K in PA and 500K in AZ
- I estimate back end size to grow steadily at about 1-2 meg per year.
The main questions I have at this point are:
1 Where to store the Tables ?
2 THe database contains OLE links to CAD drawings The Cad drawings will be stored on networks at both sites. Should I / can I create some sort of local table to store these links.
3 What is the best method of combining the tables where an autonumber PK field is used as a foreign key in relationships without disrupting the relationship.
4 Should I run the database on the AZ server and utilize the Citrix server.
Dave
gallagherd@earthlink.net
