access errors and crashes on new system

[jbhome]

Hello everyone,

My tale of woe follows
My office computer, along with the phone system, printers etc took a lightening strike last week.
The hard drive survived but not the computer.
I was able to get the office access db onto a new system but now I get errors when running it.
I'm just learning access so please forgive any terminology errors I may make.
When opened, the main menu appears. Whoopee!
Not so fast. When I select an item, I get "the expression On Click you entered as the event property setting produced the following Automation error.
The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure]

There may have been an error evaluating the function, event, or macro"

Pressing the button a second time does not produce the error and opens the correct form.
This form works properly.
The second problem is with a second report form that opens properly.
This form expects dates and accepts them but when I try to print the report, access closes with no error message.

Any thought or suggestions gratefully accepted.
both old and new systems running Xp
access ran db properly before the strike.

regards,
Jim Brooks

[June7]

Is this a split database?

Did you run Compact & Repair?

If that fails, import everything to a new db file.

Want to provide the db for analysis? Follow instructions at bottom of my post.

[jbhome]

Hello ?

As I said, I'm new so not sure what a split db is. It does have multiple records/with subfields.
I imported to a blank db but don't know (yeesh I feel like such a newb) how to make the db run.
when I open new db, I'm left in editor rather than main menu of normal running app.
Since the db contains only conf data, removing it would seem problematic. Is there a wah to delete record but leave db structure intact. Wot a newb eh.

Jim

[June7]

I presume you did not build this db?

A split database is when the data tables are in one file (backend) and another file is the user interface (frontend) that connects to the tables. This allows the data to be in a central location on a network and each user runs their own copy of the frontend. Apparently, this is not the case for you.

In the old db, check the db properties. Perhaps it was set to open a form by default when the file opened.
In Access 2003 click: Tools > Options > Current Database > set options desired

Can certainly delete records but why is this necessary?

[jbhome]

Correct, I inherited the db.

I made progress yesterday. Needed to import all part of old db. Now I was able to specify the startup form.
That opens vba ui and reports database in undefined data type.
Is there something I'm missing ie runtime libraries, to make this run?

[June7]

Possibly, again check the old db. Open the VBA editor and under Tools > References, see what libraries are selected.

[jbhome]

The preferences item in tools is greyed out. There are no modules in db, only forms and queries.

[June7]

There is no VBA code in the original db? Not even behind forms? You opened the VBA editor?

Again, do you want to provide db for analysis? Tables can be empty.