I have a stand-alone VB6 application that needs to reside on a Win2003 server along with its data so that it can be accessed from any WinXP desktop/user. I am having problems with the application finding its data files even though the file folders are in the same logical location. I am using App.Path to identify the file location, but is there something else I need to do different in a server environment?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VB6 App Convertion from Desktop to Server Based...
- Thread starter pmb55
- Start date
More information would be helpful.
1. How is the data stored, Access Database, ASCII files, etc..
2. How are you accessing the database, ADO, DAO, opening files directly.
If you are using a database with ADO, there should be a connection string somewhere in the app. i would suggest you create a login form that causes the user to select the location of the database. Make sure you store this information locally (in a file or registry settings) so that the next time the app is used, it defaults to the last location.
-George
Strong and bitter words indicate a weak cause. - Fortune cookie wisdom
1. How is the data stored, Access Database, ASCII files, etc..
2. How are you accessing the database, ADO, DAO, opening files directly.
If you are using a database with ADO, there should be a connection string somewhere in the app. i would suggest you create a login form that causes the user to select the location of the database. Make sure you store this information locally (in a file or registry settings) so that the next time the app is used, it defaults to the last location.
-George
Strong and bitter words indicate a weak cause. - Fortune cookie wisdom
macleod1021
Programmer
Something that you can do to test the validity of the App.Path is to put a breakpoint on the data access line. Then check what App.Path is.
Some things that will mess up an app is the App.Path setting is still set for the local drive. The app.path setting is configured during setup; so if you just copied the executable up to the network, it won't update. The easiest way around that problem is to install the app from a client with a UNC name (\\servername\folder). If you have to use a mapped drive letter, make sure it's available from all clients.
If that looks good in your app, then check permissions. Have someone browse out to the folder and make sure they have read and write access. Most datafiles require write access to perform any type of operation.
If this doesn't help, answer the questions from above and we should be able to give more detailed answers.
Leeland
Some things that will mess up an app is the App.Path setting is still set for the local drive. The app.path setting is configured during setup; so if you just copied the executable up to the network, it won't update. The easiest way around that problem is to install the app from a client with a UNC name (\\servername\folder). If you have to use a mapped drive letter, make sure it's available from all clients.
If that looks good in your app, then check permissions. Have someone browse out to the folder and make sure they have read and write access. Most datafiles require write access to perform any type of operation.
If this doesn't help, answer the questions from above and we should be able to give more detailed answers.
Leeland
- Thread starter
- #5
macleod1021
Programmer
OK...if you're using DAO, then it's probably an issue with the App.Path. Check that and see if that leads you to the answer.
- Thread starter
- #7
- Thread starter
- #8
- Status
