Re: Spash screens in a Access 2003 application. How?

Allen Browne wrote:
Albert has given you lots of good suggestions. Worth reading and digesting.

Here's what I generally do:
http://allenbrowne.com/ser-53.html

Essentially, you create an unbound form that is your splash screen, and set it up as your Startup so Access shows it first. The code loops for the number of seconds you specify, so you can control how long it is on screen for. During that time, it does whatever initialization you need, such as verifying that the back end tables are available. (You always split your database, don't you?)

It's almost required in A2003. Not so much in A97. I've found that splitting databases can be slower than a non-split database.

Tony's AutoFE is a godsend for fe/be apps. Makes updates a breeze.

The example splash screen also shows lots of information that is useful if you get a support call from your client. We reuse this screen for Help | About so it can stay on screen for the client when they phone. That way you know things like which version of your software they are running, which version of Access (and what service pack), who they are logged in as (useful for logging or determining their permissions), and what data file they are actually connected to.

You can download it and modify it to suit yourself.

My splash screen is very similar to yours and the data it presents. But with the information Albert and you provided, I think I'm simply going to forego a splash screen. It was nice when, in A97, I could see it when logging into the application. Access loaded after the login form was completed. With A2003 opening in full screen and then presenting the dialog, my splash screen is virtually useless. Although your solution is nice, I hate to open a form that will slow down entry into the system...even for 2 seconds. I'm simply going to put a form like my splash screen in the menu option under Help.

Thanks for the input.

.

Relevant Pages

  • RE: No data in Backend
    ... Each client has their own computer and their data is ... As I stated in my orginal question this problem of no data in the data file ... and not being able to locate the data file, ONLY occurs on Window Vista ... My database is developed using MS Access 2003 and is split. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Questions about serving database
    ... recommended a PC over a Mac. ... specs for a computer, and if my client environment is almost all mac, ... I've set up my database with a data file, ...
    (comp.databases.filemaker)
  • Re: Access Database becoming corrupt
    ... I supported a client with and access app that had close to a 1GB data file ... and 6-8 concurrent users before they moved to sql. ... Hired vendor to create inventory and sales database in ms-access. ...
    (microsoft.public.windows.server.sbs)
  • Re: Opinions needed about the best "Middleware suite" kbmMW vs. RODA
    ... kbmMW supports cross db in such way that all you need to do in your application is to set one property to switch to ... What one have to concentrate about is minimizing the amount of data moved from the app server to the client. ... C/S setup's usually have a quite active chatter going on between the client and the database, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Access 2003 Macro Security Modification
    ... the desired way to prevent the macro security warning is to ... digitally sign your database. ... Your database fileon the client computer. ...
    (microsoft.public.access.modulesdaovba)
Loading