Access crashes on Startup

[Lance]

Not sure if this is the appropriate group, but I'm going to give it a
whirl.

I have been designing an access database for about two weeks now. I
opened it up on multiple pc's when I started no problem. Today I
attempted to open it up on multiple pc's again, and now the database
crashes at startup. It still works fine on the PC I've been developing
it on, but it seems odd that it crashes on others. I am not changing
the OS, or any other factors between PCs drasticaly.

Any suggestions? Where should I even begin to troubleshoot this issue.

Thanks,
Lance

 

[Ron Hinds]

Not sure if this is the appropriate group, but I'm going to give it a
whirl.

I have been designing an access database for about two weeks now. I
opened it up on multiple pc's when I started no problem. Today I
attempted to open it up on multiple pc's again, and now the database
crashes at startup. It still works fine on the PC I've been developing
it on, but it seems odd that it crashes on others. I am not changing
the OS, or any other factors between PCs drasticaly.

Any suggestions? Where should I even begin to troubleshoot this issue.

Thanks,
Lance

You've probably added a Reference to your project for a component that
doesn't exist on the problem machine(s). If you open your db in Design view
on a problem PC (hold down the Shift key while opening), then open any code
module and click Tools | References you will probably see the word MISSING
in front of the offending component(s). You'll need to install the missing
component(s) on the problem machine(s).

 

[aaron.kempf]

a) dont use MDB for anything
b) dont use MDB across a network
c) dont use MDB when you have _ANY_ data that is confidential
d) dont let multiple people open a MDB; it's just not scalable enough
for 2 people let alone 20.

 

[Tony Toews]

a) dont use MDB for anything
Wrong.

b) dont use MDB across a network

MDBs work fine on a network.

c) dont use MDB when you have _ANY_ data that is confidential

You have a point there.

d) dont let multiple people open a MDB; it's just not scalable enough
for 2 people let alone 20.

Rubbish. MDBs work well for at least 25 people on one.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Lance]

Ron,

Thanks for your reply among the rubbish discussion that has been going
on in my thread about the usefulness of the program.

I was able to open my database in design view. However, the moment I
tried to enter any code module, or access any information from a table,
the database once again crashed. When I went back to the PC it worked
on, I noticed an obscure object in the VBA module list (where it lists
each frm, report, etc). It wasn't referencing any forms, or reports,
but was just the name of some report I had, but with a weird icon
(couldn't find the icon anywhere else, or anything explaining the
icon). The moment I tried to click on that module, access would crash
again.

What I ended up doing was just creating a new database, and importing
the entire structure. Cleared up the problem.

I have no clue what happened, wouldn't have been an issue except I
hadn't backed my work up in the last two days, and didn't feel like
replicating it.

Thanks again for your suggestion

 

[aaron.kempf]

convert to ADP and you won't have such a fragile environment

 

[BigTSmooth]

I am having the same problem you are. All 70 machines work except for this
one machine. I would hate to reload it, but it will not work for any of the
databases I have on it.

 

[Lance]

Well,

I think my problem was the reverse problem of yours. For mine, the
database became corrupt, and it would only work on the design machine,
and no others. For yours it seems you have a machine problem, as
opposed to a database problem, since no database will work on it