Do you have any application start up recommendations (or can you direct me to
a thread which may have some?

Thanks for your help!!

What are you looking for? "application start up recommendations" really
doesn't mean that much.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"laavista" <(E-Mail Removed)> wrote in message
news:1D8C90F9-BAD1-44EF-A6EE-(E-Mail Removed)...
> Do you have any application start up recommendations (or can you direct me
> to
> a thread which may have some?
>
> Thanks for your help!!

When you distribute an Access application, do you have recommendations on
"settings" that should be used?

"Douglas J. Steele" wrote:

> What are you looking for? "application start up recommendations" really
> doesn't mean that much.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
> "laavista" <(E-Mail Removed)> wrote in message
> news:1D8C90F9-BAD1-44EF-A6EE-(E-Mail Removed)...
> > Do you have any application start up recommendations (or can you direct me
> > to
> > a thread which may have some?
> >
> > Thanks for your help!!
>
>

On Thu, 16 Apr 2009 21:11:01 -0700, laavista
<(E-Mail Removed)> wrote:

>When you distribute an Access application, do you have recommendations on
>"settings" that should be used?

Turn off the Database Window, Special Keys, Default Shortcut menus,
Built-In Toolbars, Full Menus.

Set an Application Title.

Use an AutoExec Macro to start your code and display your first form.

Hold down Shift key to override these settings when you start the app
as a developer.

Create and distribute an MDE to ensure compilation, remove your source
code and prevent design changes to your forms and reports.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

laavista wrote:
> When you distribute an Access application, do you have recommendations on
> "settings" that should be used?

Distribute as split database system (front-end or "FE" and back-end or
"BE") where FE has all UI elements and BE has all data (a bit of a
simplification).

The FE on startup should open a hidden form whose recordsource is in the
BE. This forces creation of the lock file (.ldb) and maintains it for
the user "session". This improves performance in addition to providing a
way to execute code on shutdown (using the form Unload event of the
hidden form).

Hope that helps...

--
John Mishefske, Microsoft MVP 2007 - 2009
UtterAccess Editor
Tigeronomy Software
web: http://www.tigeronomy.com
email: sales ~at~ tigeronomy.com

This was extremely helpful! THANKS!

"Armen Stein" wrote:

> On Thu, 16 Apr 2009 21:11:01 -0700, laavista
> <(E-Mail Removed)> wrote:
>
> >When you distribute an Access application, do you have recommendations on
> >"settings" that should be used?
>
> Turn off the Database Window, Special Keys, Default Shortcut menus,
> Built-In Toolbars, Full Menus.
>
> Set an Application Title.
>
> Use an AutoExec Macro to start your code and display your first form.
>
> Hold down Shift key to override these settings when you start the app
> as a developer.
>
> Create and distribute an MDE to ensure compilation, remove your source
> code and prevent design changes to your forms and reports.
>
> Armen Stein
> Microsoft Access MVP
> www.JStreetTech.com
>
>

Thank you so much. Great advice!

"John Mishefske" wrote:

> laavista wrote:
> > When you distribute an Access application, do you have recommendations on
> > "settings" that should be used?
>
> Distribute as split database system (front-end or "FE" and back-end or
> "BE") where FE has all UI elements and BE has all data (a bit of a
> simplification).
>
> The FE on startup should open a hidden form whose recordsource is in the
> BE. This forces creation of the lock file (.ldb) and maintains it for
> the user "session". This improves performance in addition to providing a
> way to execute code on shutdown (using the form Unload event of the
> hidden form).
>
> Hope that helps...
>
> --
> John Mishefske, Microsoft MVP 2007 - 2009
> UtterAccess Editor
> Tigeronomy Software
> web: http://www.tigeronomy.com
> email: sales ~at~ tigeronomy.com
>