|
-
Nov 30th, 2011, 05:36 PM
#8
Re: Connection string not working when deployed...
Exactly.
My guess is it fails because the file name has spaces, or may even be based on App.Path and ends up having "Program Files (x86)" within it. Simply adding quotes would take care of it, and in this case even apostrophes (') will work.
Then UAC and file virtualization will probably be his next stumbling block.
Or we could be all wet and the problem is somewhere else.
The use of redundant parens on the .Open call and that trailing semicolon in the connection string don't bode well. There may be other time bombs in his code.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|