 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Developer Toolkits / September 2005Packaging wizard problem - repost
Hi all, I've just started using the Office XP Packaging Wizard. When I start it and add a database file (Access 2002 format), I get the following: The file that you specified could not be opened. Possible reasons for this include: -Access is not installed on your computer. -The version of Access installed on your computer is not compatible with this file. The file you specified is not a valid Access file. I have multiple versions of access installed (97,2000, XP and 2003). Could this be causing confusion? Any ideas, anyone? I'm replying because no-one else has. I can't reproduce that problem (2002). I can add any file, I can even add a txt file renamed as mdb (makes Access think a bit!), or a 97 mdb. If I add a file that's busy I get an appropriate message. I can't do better than your own suspicion. I would think it's a bit dangerous to create packages with multiple versions of Access installed, regardless of wherther it works, how do you know the correct dll versions are being packaged? Chris > Hi all, > [quoted text clipped - 12 lines] > > Any ideas, anyone? I had a vague thought to check the mdb file association is pointing to the desired version of Access. Chris I had the same problem as Paul and cured it by directing the Access file at the correct version in "FileTypes" I agree that having multiple versions of Access on your development machine is dangerous. As I don't know which version my customers might have, I develop om A2000. If I am distributing run-time with my apps, then A2002 run-time is packaged. > I had a vague thought to check the mdb file association is pointing to the > desired version of Access. > > Chris > I agree that having multiple versions of Access on your development machine > is dangerous. > > As I don't know which version my customers might have, I develop om A2000. > If I am distributing run-time with my apps, then A2002 run-time is packaged. Just to clarify, I was referring to developing/packaging in regards to multiple versions on a PC. I have no untoward problems with multiple versions on the end-user PC. My main distribution is A2000, regardless of later Access they may have. Works fine. If you are distributing exact same with A2002 runtime packaged, and not the mdb/mde converted, one of the references MUST change (Microsoft Access x Object Library). Therefore, the mdb must be running decompiled (and I'm not sure about mde) I don't consider running an mdb/mde on anything other than the version of Access I have designed and/or tested it for. Chris :-) I had that error when trying to run packaging wizard. I solved it! If your app is protected by a system.mdw workgroup file, you MUST join that workgroup before running the packaging wizard. Once I did that, everything worked fine. Kathy Webster > I'm replying because no-one else has. > [quoted text clipped - 32 lines] >> >> Any ideas, anyone? I had that error when trying to run packaging wizard. I solved it! If your app is protected by a system.mdw workgroup file, you MUST join that workgroup before running the packaging wizard. Once I did that, everything worked fine. Kathy Webster > Hi all, > [quoted text clipped - 15 lines] > > Any ideas, anyone? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.