BigDaveStafford
asked on
Database deploys as read-only
Hello,
Have been making great progress on an split database application thanks to many questions and helpful answers from the experts.
One last problem and then I think I'm done!
My application has a front end and then a couple of back-end databases. The purposes of having a couple of back-ends is to provide some sample data for the user to play with and the other is for the user's real data.
I've used the package and deploy wizard to copy and install all the necessary files. I've then copied all the install files onto a CD from which the user can install the application. The installation seemingly works well and all the tables are properly relinked, etc. However, the back-end appears to be copied to the installation folder with read-only attributes (presumably because is was installed from a read only source?). Consequently, the forms and queries throw up error after error because nothing can be written to the back-end file.
The issue doesn't appear with the first back-end, it's only after I restore the second back-end that this problem occurs. It doesn't occur when I restore the same back-end on the development installation of the application.
I had thought that I could use the filesystem object functionality to reset the attributes after files are copied to the installation folder, but this seems really cumbersome.
Any ideas on either (a) preventing the problem from occuring or (b) changing the attributes on the file after it has been installed?
Many thanks in advance and many thanks for all the help so far. You guys rock!
Cheers
Have been making great progress on an split database application thanks to many questions and helpful answers from the experts.
One last problem and then I think I'm done!
My application has a front end and then a couple of back-end databases. The purposes of having a couple of back-ends is to provide some sample data for the user to play with and the other is for the user's real data.
I've used the package and deploy wizard to copy and install all the necessary files. I've then copied all the install files onto a CD from which the user can install the application. The installation seemingly works well and all the tables are properly relinked, etc. However, the back-end appears to be copied to the installation folder with read-only attributes (presumably because is was installed from a read only source?). Consequently, the forms and queries throw up error after error because nothing can be written to the back-end file.
The issue doesn't appear with the first back-end, it's only after I restore the second back-end that this problem occurs. It doesn't occur when I restore the same back-end on the development installation of the application.
I had thought that I could use the filesystem object functionality to reset the attributes after files are copied to the installation folder, but this seems really cumbersome.
Any ideas on either (a) preventing the problem from occuring or (b) changing the attributes on the file after it has been installed?
Many thanks in advance and many thanks for all the help so far. You guys rock!
Cheers
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I thought that might be the issue. For the time being I must distribute the setup package on CD, although I guess I could create a self-extracting zip file and email it to users.
I'll have to work on the web distribution idea.
Many thanks
Dave