 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Developer Toolkits / May 2007Some problems when I create Access 2003 Runtime
Hi, It is my first time to use Access 2003 Developer's Kit to create Access 2003 runtime. We just convert Access 97 programs to Access 2003. I encounter a number of problems 1) When I invoke the Access 2003 runtime front end, I get an error message saying that I have to download Jet 4.0 SP8. However, when I attempt to install it on a Windows XP SP2 workstation, it mentions that the system is of later version than the patch. I would like to know the reason for getting this error message is because the connection between Access 97 FE / BE is different from Access 2003 FE / BE ? 2) I have attempted to remove the Access 2003 front end from the workstation. I have tried the following but without success. a) From Add/Remove Program - Uninstall Access 2003 Runtime b) From the setup (the one used to install the Access 2003 Runtime FE) and delete I find that the runtime is still there as I can open any Access 2003 Database successfully (Of course, only the features of Runtime is available). Your advice is sought. Regards, Peter > 1) When I invoke the Access 2003 runtime front end, I get an error message > saying that I have to download Jet 4.0 SP8. However, when I attempt to > install it on a Windows XP SP2 workstation, it mentions that the system is > of later version than the patch. I would like to know the reason for > getting this error message is because the connection between Access 97 FE > / BE is different from Access 2003 FE / BE ? I would suggest that you place the following two registry entrees in your install, and that way, all of the nag prompts you get when you launch access 2003 will go away ROOT:Local Machine Key: SOFTWARE\Microsoft\Jet\4.0\Engines Name:SandBoxMode Value:#00000002 ROOT:Local Machine Key: Software\Microsoft\Office\11.0\Access\Security Name:Level Value:#00000001 If you add both of the above, then you get no security prompts at all...even if the later jet sp8 is NOT installed. It is clean...and no prompts.... > 2) I have attempted to remove the Access 2003 front end from the > workstation. I have tried the following but without success. [quoted text clipped - 5 lines] > Database successfully (Of course, only the features of Runtime is > available). It is possible that other applications have installed a runtime also. (there is quite a few commercial programs that use the runtime). Regardless, you much better off to separate your runtime install from the front end or mde install. Remember, the runtime is NOT different then the full version (except for no design mode, and you need to provide custom menus). Further, there is "no" special connection between the runtime, ad the mde that you deploy. Once you install the runtime, then it is a simple matter to copy any mdb, or mde to that target machine. In fact, I would STRONGLY suggest that you separate the two installs, since why send, or install a 34 meg runtime when there is a good chance it is on the target machine already? further, unless your a perfect coder, you will need to provide FREQUENT updates to your front end,a nd again it just a silly waste of time to throw in the runtime when you all you really need is to provide a new mde. So, to get rid of the prompts, add those registry entrees to the package your create with the wizard. And, really..stop including your mde with the installs you make. (separate them). By sepeating the two, you can provide really fast and easy updates. Here is a set of screen shots as to how I update my users front ends: http://www.kallal.ca/ridestutorialp/upgrade.html I actually use the free inno installer (but, really, the front end updates are really a simple file copy, and you don't need the hassles that the package wizard involves when updating that simple mde file).  SignatureAlbert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com Dear Albert, Thank you for your advice. I have created a package with ADE for installing MS Access 2003 runtime. I would like to seek your advice on how to copy the Front End database across. Do you suggest using the ADE wizard or Inno Installer ? If you suggest ADE wizard, I would like to know how to handle the following issues ? 1) When I create a package, I find that I have to change the SID for different databases (Otherwise, when I install the second database, it says that it already exists. Is it correct ? 2) I don't know for a later version of FE, is it necessary for me to remove the existing version only ? If both of them carry the same version (I don't change the version 1.0.0.0 in ADE wizard, will it cause any problem ? 3) Does it require administrative right to install the FE ? 4) I put the FE in "C: \ Program Files \ Common File" \ MSACCESS. Is it OK ? Your advice is sought ! Regards, Peter >> 1) When I invoke the Access 2003 runtime front end, I get an error >> message saying that I have to download Jet 4.0 SP8. However, when I [quoted text clipped - 61 lines] > are really a simple file copy, and you don't need the hassles that the > package wizard involves when updating that simple mde file). > I would like to seek your advice on how to copy the Front End database > across. Do you suggest using the ADE wizard or Inno Installer ? I actually suggest using inno. There is actually a bug in the a2003 PW that generates wrong shortcut for you desktop anyway (they are wrong if the a2003 runtime installs into a non default directory...which will occur if the end machine has a custom office install to a non standard dir. > If you suggest ADE wizard, I would like to know how to handle the > following issues ? > 1) When I create a package, I find that I have to change the SID for > different databases (Otherwise, when I install the second database, it > says that it already exists. Is it correct ? Yes, the above is one great reason why I don't use the PW. > 2) I don't know for a later version of FE, is it necessary for me to > remove the existing version only ? If both of them carry the same version > (I don't change the version 1.0.0.0 in ADE wizard, will it cause any > problem ? You have to try the above, I reasonable sure that you can just change the SID, but then I think you will actually create a "remove" entry in the "add/remove" programs list for EACH time you install. You don't want that... I tried testing this, because I gave up...and moved to inno.. > 3) Does it require administrative right to install the FE ? no, quite sure you don't need admin rights. > 4) I put the FE in "C: \ Program Files \ Common File" \ MSACCESS. Is it > OK Well, I used to use c:\program files\NyApplicationName\ However, some companies are now locking down any changes to program files (and, vista also this way). So, as a future proof dir, I started using: "C:\Documents and Settings\All Users\Application Data\Rides\RidesXP.mdb" So, my application name is "Rides", and I install into a dir called "rides" So, I don't recommend c:\program files\ anymore, this is due to some of my customers locking down (read only) for that dir. And, vista is much the same way. This also eliminates the issue of admin privileges, as often that why c:\program files is locked down... Your choice of "common" files is ok I suppose, but I an avoiding the program dir these days... SignatureAlbert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com > ? > [quoted text clipped - 68 lines] >> updates are really a simple file copy, and you don't need the hassles >> that the package wizard involves when updating that simple mde file). Is there a way of making these registry entries using code be it access, vbscript or .net? >> 1) When I invoke the Access 2003 runtime front end, I get an error >> message saying that I have to download Jet 4.0 SP8. However, when I [quoted text clipped - 61 lines] > are really a simple file copy, and you don't need the hassles that the > package wizard involves when updating that simple mde file). Dear Mark, I have no previous experience with .NET. Peter > Is there a way of making these registry entries using code be it access, > vbscript or .net? [quoted text clipped - 64 lines] >> updates are really a simple file copy, and you don't need the hassles >> that the package wizard involves when updating that simple mde file). |
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.