If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
How to avoid hard-coding the DB folder path?
What's the best way to I need to write a little Access application to collect data for later analysis. I will be hiring some high school kids to do the actual data entry. They will be working on it over the summer. I want to separate the application code from the database tables so that I can send out updates to the code without sending out the tables and obliterating what they have already entered. Let's say I create DataEntryCode.mdb (containing the code) and DataEntryData.mdb containing the data. Is there a way to code the path info for the database module (DataEntryData.mdb) in the code module (DataEntryCode.mdb) so that it looks in whatever folder it resides in and not in a hard coded place. I want the application to still work if it is moved to a different folder. I am running Access 2000, but I could upgrade to a later version if that would make a difference. Thanks -- Running MS Office 2K Pro on Win2K-SR2 on an HP Omnibook 6000 laptop connected over a P2P network to an HP Vectra workstation For email, use Usenet-20031220 at spamex.com |
#2
|
|||
|
|||
How to avoid hard-coding the DB folder path?
Take a look at the code in http://www.mvps.org/access/tables/tbl0009.htm at
"The Access Web". It prompts you to look for where the back-end is located, and will relink as necessary. -- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (No private e-mails, please) "Top Spin" wrote in message ... What's the best way to I need to write a little Access application to collect data for later analysis. I will be hiring some high school kids to do the actual data entry. They will be working on it over the summer. I want to separate the application code from the database tables so that I can send out updates to the code without sending out the tables and obliterating what they have already entered. Let's say I create DataEntryCode.mdb (containing the code) and DataEntryData.mdb containing the data. Is there a way to code the path info for the database module (DataEntryData.mdb) in the code module (DataEntryCode.mdb) so that it looks in whatever folder it resides in and not in a hard coded place. I want the application to still work if it is moved to a different folder. I am running Access 2000, but I could upgrade to a later version if that would make a difference. Thanks -- Running MS Office 2K Pro on Win2K-SR2 on an HP Omnibook 6000 laptop connected over a P2P network to an HP Vectra workstation For email, use Usenet-20031220 at spamex.com |
#3
|
|||
|
|||
How to avoid hard-coding the DB folder path?
On Wed, 5 May 2004 20:54:24 -0400, "Douglas J. Steele"
wrote: Take a look at the code in http://www.mvps.org/access/tables/tbl0009.htm at "The Access Web". It prompts you to look for where the back-end is located, and will relink as necessary. Thanks -- Running MS Office 2K Pro on Win2K-SR2 on an HP Omnibook 6000 laptop connected over a P2P network to an HP Vectra workstation For email, use Usenet-20031220 at spamex.com |
Thread Tools | |
Display Modes | |
|
|