moose
Oct 9th, 2000, 03:42 PM
Bear with me here....It's going to be a tough explanation.
I have a VB program that uses an access backend to store data. What I am trying to do is avoid hard coding the location of the database directly into VB (encase the location of the program changes). For instance, I am using this program in 2 different offices. So I had to create 2 different exe files, one with the path for office A and the other for the path of office B. What I am hoping to do is install the database in the same folder with the exe and everything run ok without hard coding the location.
I know this has to be possible. I'm just not sure what it is or what it is even called. Can you shed some light on this?
I have a VB program that uses an access backend to store data. What I am trying to do is avoid hard coding the location of the database directly into VB (encase the location of the program changes). For instance, I am using this program in 2 different offices. So I had to create 2 different exe files, one with the path for office A and the other for the path of office B. What I am hoping to do is install the database in the same folder with the exe and everything run ok without hard coding the location.
I know this has to be possible. I'm just not sure what it is or what it is even called. Can you shed some light on this?