Replies

I like Patt’s zip idea.

Here is another. If your database is the only one that will contain all the data from all the dens on one table you could create a primary key for each den to use. Maybe (Den#, Scout#, AwardDate, Award, LstName).

You could add code to query the awards time period and export the data to an Excel file or any file format of your choice. Easily emailed due to its small size or again you could zip it. If you choose to stay with the floppy, file transfer is faster.

I may be missing something here but is there a reason you do not have the database on a network? Your sneakernetting time would be cut down if your BE was on a network and I think there would be less chance for an error or corruption to occur.

Am I sure…no. The message box that pops up indicates the trouble is with words execute file.

Are you using the floppy as a backup for the database? If so, why not just write over the old .mdb?

Try “Error Codes” in the help file in Access 97. Copy the code to a module and run it. The code will create a table “AccessAndJetErrors.” The table will contain two fields, Error Code, and ErrorString, which is the description of the error code.

Bummer. I had hoped there was a way.

MSWord (Office97) is opened and closed programmatically from within Access 97.