Access 97 - The database msched.mdb needs to be repaired

[Alan H.]

I have a Access 97 application that has run well for approximately 5 years
and has corrupted approximately 5 times in past the 6 weeks . The app has not
been revised since 2002. I have found that I can consistently generate this
corruption by running a menu option that runs a macro to generate a monthly
report, which prompts for a start date and end date, and generates an Excel
97 spreadsheet with 3 worksheets, The macro calls Open Form > Pop Up
Calendar, Transfer Spreadsheet C:\master scheduler\accounting.xls, Transfer
Spreadsheet C:\master scheduler\accounting.xls, Transfer Spreadsheet
C:\master scheduler\accounting.xls, Transfer Spreadsheet C:\master
scheduler\accounting.xls
CloseForm, MsgBox

I think this may be caused by the calendar control function - I skipped the
calendar start and end date selections on one test and app didn't crash but
generated an empty spreadsheet.

There may be other causes of these corruptions, however, I have not
determined them yet.

The users in question are all running Office 2003 on Win XP except for one
running Office 2000 on Win 2000.

If anyone has any ideas on how I can correct this problem, please let me
know. Thanks.

 

[Arvin Meyer [MVP]]

Try replacing the calendar control with the Access calendar form at:

http://www.datastrat.com/Download/Calendar97.zip

Also, make sure that the form you are running the code from is not corrupt.
You can try decompiling, then recompiling the code. Make sure that you have
first made a copy:

http://www.mvps.org/access/bugs/bugs0008.htm

 

[Alan H.]

Hello Arvin,

I tried using the new calendar control and ended up with the same result. I
may have not linked the new calendar control in correctly.

I recompiled the whole application to generate a mde file. The app seems to
run OK as an mde file. We originally ran this app as an mde file and later
decided to run it as an mdb file. I cannot recall why we did this. Will I be
introducing other problems by doing this?

Thanks.

 

[Arvin Meyer [MVP]]

You shouldn't have any problem in any version of Access using the calendar
form. You do need to import both the form and the module. That form
(converted) works in every mdb and mde version of Access from 2.0 through
2007.

You may have had another corruption problem that was exacerbated by the
calendar or calendar control. Compiling into an mde will force you to clean
up the corruption.

As long as you maintain the original file, you can run and mde. Once you've
discarded the mdb, you are forever stuck.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[Alan H.]

My application seems to run fine as a mde file except for one form. The form
requests a date in a drop down list and defaults to the current date. On a
non administrator Windows PC using either a Administrator/Non administrator
Access account - the default date shows a date back in 2000 - when the app
was installed. When I attempt to change the date to the current date, the
following error appears:

The expression Date you entered in the form control's ValidationRule
property contains the error The function you entered can't be used in this
expression.

The Form has the following settings: Default Date = Date() and Validation
Rule <= Date(). This PC's date is showing todays date: September 10, 2007.

The mde works fine on my PC - when I log in as a Windows administrator or
Windows non administrator. The mdb version of this app doesn't have this form
issue on this PC.

Thanks for your help. Please let me know.

 

[John W. Vinson]

The expression Date you entered in the form control's ValidationRule
property contains the error The function you entered can't be used in this
expression.

The Form has the following settings: Default Date = Date() and Validation
Rule <= Date(). This PC's date is showing todays date: September 10, 2007.

Where do you have

Default Date = Date()

in your form? Is the name of your table field Date? If so, Access is getting
confused! That's a reserved word, because Access can't tell if you mean the
fieldname or the Date() function.

John W. Vinson [MVP]

 

[Alan H.]

I have this defined in a combo box called Date - in a form. I actually have
Default Value = Date().

The row source is defined as SELECT DatesOfTheYear.DatesOfTheYear FROM
DatesOfTheYear; The table DatesOfTheYear has one field called DatesOfTheYear
which has a data type of Date/Time.

What I'm unclear about is this Combo Box popluates correctly for Access 97
users with administrative priveleges and not for unpriveleged Access 97 users.

Thanks.

 

[John W. Vinson]

What I'm unclear about is this Combo Box popluates correctly for Access 97
users with administrative priveleges and not for unpriveleged Access 97 users.

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.

John W. Vinson [MVP]