Application Start Up Recommendations?

[laavista]

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

Thanks for your help!!

 

[Douglas J. Steele]

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

 

[laavista]

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

 

[Armen Stein]

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

 

[John Mishefske]

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

 

[laavista]

This was extremely helpful! THANKS!

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]

Thank you so much. Great advice!

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