By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,790 Members | 1,407 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,790 IT Pros & Developers. It's quick & easy.

Run application from a Jump drive

P: 443
I've had a request for a user wanting to know if my application can be installed on a jump drive do he can take the jump drive to different computers and run it. In my application I extract files out to the C: this wouldn't create a problem but not sure what other problems the jump drive might cause. How would I go about making sure that my application would be able to know the drive location of the jump drive seeing that it might be different on different computers. Has anybody out there tried this?
Thanks for any suggestions.
Feb 16 '09 #1
Share this Question
Share on Google+
3 Replies

Expert 100+
P: 489
Hi Tom,

The following code would give you the drive name in a string format that you are running your application from. If the app is going to be run from an UNC path then you would have to add some more code to check for that as well.

Expand|Select|Wrap|Line Numbers
  1. left(currentproject.Path,3)
If your DB path was "C:\Projects\MyProjects\xxx\DB1.mdb", you would get a string of "C:\" returned. But if the path was "\\myserver\projects....." all you would get back is "\\m".

Welcome to Bytes.
Feb 16 '09 #2

Expert 2.5K+
P: 3,532
I troll thru this forum and four other Access forums/newsgroups, an average of 8-10 times a day, and the week never goes by without my seeing one or two threads dealing with chronic corruption when trying to run a database using removable storage devices. I have never seen any response that comes even close to explaining the cause of the problem. The only thing that comes to mind is, perhaps, the way data is accessed thru these devices. Access databases tend to become corrupt when connectivity to the back end is interrupted.

If I were doing this, I'd copy the data to the PC being used, run the app, then copy the data back to the removable drive, leaving a copy on the PC. This will give you a fall back position should something go awry.

Linq ;0)>
Feb 16 '09 #3

P: 443
I'm able to run the program on the jump drive but I think if what your saying about the currupt database I might let this user know that it's not advisable to do it this way and the if the database gets currupt I'm not responsible. The program has a way to backup the data and restore it on different machines and that's the way most users move from one machine to another. Thanks for the advise.
Feb 16 '09 #4

Post your reply

Sign in to post your reply or Sign up for a free account.