JoeyCode
May 3rd, 2000, 09:35 AM
Hey Everybody,
I'm trying to figure out the easiest, least hassle way to solve this issue I've got, maybe some of you can help.
I'm creating an attendance system for use in small schools. I'm using VB6 for the user interface and Access 97 for the database, connecting with DAO. What I want to do is have a single Access DB that contains only the data tables (call this the "DATA" DB), and have another Access DB that links the tables from the DATA DB and contains all the queries and whatever other junk I need to put into Access (call this the "MAIN" DB). I want to do this so that if any of the stuff in MAIN needs to be updated, I can do so without disturbing the actual DATA.
Originally I wanted to have just a single MAIN DB that all the machines connected to, but since Access stores the full path of the linked DATA tables, only the machine that has the DATA DB on it (essentially the file server) would be able to use it. So this means each machine needs its own copy of the MAIN DB with its own unique linking info. The problem with this is that the only way I can find to link tables in Access is to do it within Access itself. This is a problem because I can't pre-link the tables due to the fact that I will have no idea ahead of time where the DBs will be located, and Access will not be available to do linking at installation time. But even if it was, this doesn't allow the databases to be moved very easily.
What I'd like to be able to do is to have my VB front-end, that knows the locations of all the DBs, to be able to tell the MAIN DB at any time to unlink and relink the DATA DB tables. However, I haven't been able to find a way to do this. I'm thinking it's not possible, and I wonder how others have gotten around these issues. There's so little information available on this topic that I've been able to find out there that I'm considering just consolidating the DATA and MAIN DBs together and be done with it. But I don't want to do that if there are any other options. Anybody know of a way I can dynamically link tables, or some other way to solve these issues without having to go to a single DB or immensely complicate the installation and maintanence of this system?
Thanks for your help,
-JoeyCode
I'm trying to figure out the easiest, least hassle way to solve this issue I've got, maybe some of you can help.
I'm creating an attendance system for use in small schools. I'm using VB6 for the user interface and Access 97 for the database, connecting with DAO. What I want to do is have a single Access DB that contains only the data tables (call this the "DATA" DB), and have another Access DB that links the tables from the DATA DB and contains all the queries and whatever other junk I need to put into Access (call this the "MAIN" DB). I want to do this so that if any of the stuff in MAIN needs to be updated, I can do so without disturbing the actual DATA.
Originally I wanted to have just a single MAIN DB that all the machines connected to, but since Access stores the full path of the linked DATA tables, only the machine that has the DATA DB on it (essentially the file server) would be able to use it. So this means each machine needs its own copy of the MAIN DB with its own unique linking info. The problem with this is that the only way I can find to link tables in Access is to do it within Access itself. This is a problem because I can't pre-link the tables due to the fact that I will have no idea ahead of time where the DBs will be located, and Access will not be available to do linking at installation time. But even if it was, this doesn't allow the databases to be moved very easily.
What I'd like to be able to do is to have my VB front-end, that knows the locations of all the DBs, to be able to tell the MAIN DB at any time to unlink and relink the DATA DB tables. However, I haven't been able to find a way to do this. I'm thinking it's not possible, and I wonder how others have gotten around these issues. There's so little information available on this topic that I've been able to find out there that I'm considering just consolidating the DATA and MAIN DBs together and be done with it. But I don't want to do that if there are any other options. Anybody know of a way I can dynamically link tables, or some other way to solve these issues without having to go to a single DB or immensely complicate the installation and maintanence of this system?
Thanks for your help,
-JoeyCode