Startup problem with runtime and no-runtime apps DaBartman 11.07.2006 16:24:01 This problem just cropped up about 10 days ago. When starting a program I get the security warning dialog (No, Open, More Information). Normally clicking Open allows the program to begin at it's startup page. I am using my switchboard which for my app is the most logical place to begin and has worked very well in the past. Now when I click Open the screen blanks out, leaving me with a dark gray Access background. On a no-runtime version if I click File-->Application name from the list at the bottom of File, the program starts and runs normally. With a runtime version I can't do this as I set the menu properties to only display a minimum of options on the menu bar. This program is eventually going to be sold via the internrt. Obviously, these problems (Security Warning dialog and the blanking out at startup time). I can probably solve the first by setting my security settings a bit looser, but after searching several thousand pages of documentation and many hours in the Help system I am at a loss. If any of you folks are familiar with this behavior I would be quite grateful if you could share any solutions with me. With much thanks, Bart

Re: Startup problem with runtime and no-runtime apps Scott McDaniel <scott[ at ]NoSpam_Infotrakker.com> 11.07.2006 21:06:12 On Tue, 11 Jul 2006 09:24:01 -0700, DaBartman <DaBartman[ at ]discussions.microsoft.com> wrote: [Quoted Text] >This problem just cropped up about 10 days ago. When starting a program I get >the security warning dialog (No, Open, More Information). Normally clicking >Open allows the program to begin at it's startup page. I assume you're talking about the "This file may not be safe" warning? If so, you'll need to digitally sign your project, especially if you'll be deploying this via the internet. You'll want to purchase a code signing certificate from one of the trusted vendors and then use that to "sign" your installation file (the .exe file you produce to install your application). Comodo is one: http://www.instantssl.com/code-signing/ Verisign is another: http://www.verisign.com/products-services/security-services/code-signing/digital-ids-code-signing/index.html). MSDN info on signing a VBA project: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odeopg/html/deovrsigningvbaproject.asp If you're talking about the "Unsafe Experssions" warnings, that's a different story. This could be caused by a number of things, including not having the correct version of Jet on your machine. Here's a link which may help with that: http://office.microsoft.com/en-ca/assistance/HA011225981033.aspx I am using my >switchboard which for my app is the most logical place to begin and has >worked very well in the past. Now when I click Open the screen blanks out, >leaving me with a dark gray Access background. On a no-runtime version if I >click File-->Application name from the list at the bottom of File, the >program starts and runs normally. With a runtime version I can't do this as I >set the menu properties to only display a minimum of options on the menu bar. >This program is eventually going to be sold via the internrt. Obviously, >these problems (Security Warning dialog and the blanking out at startup >time). I can probably solve the first by setting my security settings a bit >looser, but after searching several thousand pages of documentation and many >hours in the Help system I am at a loss. If any of you folks are familiar >with this behavior I would be quite grateful if you could share any solutions >with me. With much thanks, Bart When you say "runtime" version, do you mean an Access application opened using the /runtime switch, or opened using the Access runtime? Or do you mean an Access application that you've converted to the .mde format? The Runtime is basically Access without the design features. There are several things that can cause problems with a Runtime deployment. Did you try to run your app on your development machine? If you did not, and instead transferred you app to a different machine for testing, you may have a reference problem. You'd need to verify that the references on your enduser machine match those of your development machine and, if they don't, you'll have to distribute the necessary files to make them matchup. Here's a link to an MSDN section that talks at length about various deployment strategies, best practices, etc ... (look for the Access 2003 Developer Extensions section, specifically the first 2 links in that section: http://msdn.microsoft.com/office/program/access/2003/reference/article/ Scott McDaniel scott[ at ]takemeout_infotrakker.com www.infotrakker.com