Quick Recovery, reset the references, split database

[Janis]

I have a split front-end and back-end that crashes every time a report runs
and there are 3 of them. They are run from a report menu with 3 toggle
switches.
I am following the list of what to do for Allen Brown's Quick Recovery. It
did not have Name Auto Correct box checked so I left it unchecked. I
compacted, decompiled and compacted again. I have a split database. Does
that mean I have to perform the quick recovery steps on both files?

NOw to set the minimal references. It has the following:
1. Visual Basic for Applications
2. Microsoft Access 11.0 Object Library
3. Microsoft DAO 3.6 Object Library
4. Microsoft Forms 2.0 Object Library
5. OLE Automation
6.Microsoft Visual Basic for Applications Extensibility 5.3

I don't know enough about references to know if this is right or not.

I have one other question. Besides this quick recover, I was going to use a
script that will compact the database after every time the report is run.
That way Access will never crash.
thanks,

 

[Gina Whipp]

Janis,

The first thing I would check for is if there is a default Printer
installed. Without it I have heard of the systems you describe.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Janis]

Thanks for the tip. Very likely you are right it involves the default
printer since it does seem to be connected to only the reports. I will
check that when I get to the office. However, since it has crashed
repeatedly it should still be recovered right? I still need to know if you
have to run recovery on the backend and frontend.
thanks,

 

[huangda 晋江兴达机械]

I have a split front-end and back-end that crashes every time a report runs
and there are 3 of them. They are run from a report menu with 3 toggle
switches.
I am following the list of what to do for Allen Brown's Quick Recovery.
It
did not have Name Auto Correct box checked so I left it unchecked. I
compacted, decompiled and compacted again. I have a split database. Does
that mean I have to perform the quick recovery steps on both files?

NOw to set the minimal references. It has the following:
1. Visual Basic for Applications
2. Microsoft Access 11.0 Object Library
3. Microsoft DAO 3.6 Object Library
4. Microsoft Forms 2.0 Object Library
5. OLE Automation
6.Microsoft Visual Basic for Applications Extensibility 5.3

I don't know enough about references to know if this is right or not.

I have one other question. Besides this quick recover, I was going to use
a
script that will compact the database after every time the report is run.
That way Access will never crash.
thanks,

 

[Gina Whipp]

Janis,

Since you indicate you can still get into it I would set the default
printer, open it and run a compact and repair. I cannot answer the
"...still be recoverable..." because there are too many reasons why it
wouldn't be having nothing to do with your issue. Let's keep our finger
(and toes) crossed that it's just a default printer issue.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[John W. Vinson]

I still need to know if you
have to run recovery on the backend and frontend.

It should not be necessary to do anything with the backend if it is in fact
the printer issue - or until you have demonstrable problems with the backend
(alone, or from a different frontend). You do need good backups of both front
and back ends in any case, and - given a good current backup! - it shouldn't
HURT to compact and repair the backend, but it probably isn't required either.

 

[Tony Toews [MVP]]

Since you indicate you can still get into it I would set the default
printer, open it and run a compact and repair.

Sometimes wierdnesses get fixed by an import into a new MDB/ACCDB
file. Compact and repair really only fixes up tables and indexes
although it might do some object stuff.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Gina Whipp]

Tony,

True but her "problem" seems to be related to a default printer and after so
many "crashes" a compact and repair won't hurt. After so many "crashes" I
would want to run one just to reclaim whatever lost space I will get back
and fix any minor issues that MIGHT have arisen. If it goes beyond that,
you're right compact and repair is not the best choice depending on the
issue. Then I start with ... go to these sites and follow these
instructions..."

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Tony Toews [MVP]]

I have a split front-end and back-end that crashes every time a report runs
and there are 3 of them. They are run from a report menu with 3 toggle
switches.

Do these crash on all systems or just yours? Do all reports crash or
just these three? What happens if you create a blank one page report
and try to print that?

NOw to set the minimal references. It has the following:
1. Visual Basic for Applications
2. Microsoft Access 11.0 Object Library
3. Microsoft DAO 3.6 Object Library
5. OLE Automation

The above four are standard

6.Microsoft Visual Basic for Applications Extensibility 5.3
4. Microsoft Forms 2.0 Object Library

You almost certainly don't need those. After removing them compile
the code though.

I have one other question. Besides this quick recover, I was going to use a
script that will compact the database after every time the report is run.
That way Access will never crash.

Shouldn't be necessary. But this implies then that the reports don't
crash Access the first time you run them but do crash the second time
you run them. Is this correct?

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

I have a split front-end and back-end that crashes every time a report runs
and there are 3 of them. They are run from a report menu with 3 toggle
switches.

Do these crash on all systems or just yours? Do all reports crash or
just these three? What happens if you create a blank one page report
and try to print that?

NOw to set the minimal references. It has the following:
1. Visual Basic for Applications
2. Microsoft Access 11.0 Object Library
3. Microsoft DAO 3.6 Object Library
5. OLE Automation

The above four are standard

6.Microsoft Visual Basic for Applications Extensibility 5.3
4. Microsoft Forms 2.0 Object Library

You almost certainly don't need those. After removing them compile
the code though.

I have one other question. Besides this quick recover, I was going to use a
script that will compact the database after every time the report is run.
That way Access will never crash.

Shouldn't be necessary. But this implies then that the reports don't
crash Access the first time you run them but do crash the second time
you run them. Is this correct?

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/