Hi guys, I have a problem that's been bugging me for ages and I' hoping someone will be able to help me out.
I have written VB.Net front-end to an access database. Running on my development computer, it's fine because the path to the database is hard-coded (ie: D:\VBProjects\Datasource\data.mdb).
However, as soon as I copy the EXE (even if using the deployment wizard and including the MDB source files) to another PC, and run it - it always generates an error because the path to the MDB can not (obviously) be found - as it's still looking in the original location (ie: D\VBProjects... etc).
My question is this. Other than creating folders of the same name on the remote PC, so that the path is found - how can I make it so that the MDB is picked up automatically, or even code it so that I can deploy my database front end EXE to several PC's and store the database on just one PC?
It's driving me mad and if anyone has the answer, I will forever be in their debt!
Thanks,
Shifty.
I have written VB.Net front-end to an access database. Running on my development computer, it's fine because the path to the database is hard-coded (ie: D:\VBProjects\Datasource\data.mdb).
However, as soon as I copy the EXE (even if using the deployment wizard and including the MDB source files) to another PC, and run it - it always generates an error because the path to the MDB can not (obviously) be found - as it's still looking in the original location (ie: D\VBProjects... etc).
My question is this. Other than creating folders of the same name on the remote PC, so that the path is found - how can I make it so that the MDB is picked up automatically, or even code it so that I can deploy my database front end EXE to several PC's and store the database on just one PC?
It's driving me mad and if anyone has the answer, I will forever be in their debt!
Thanks,
Shifty.