Access corruption

[Deitzingham]

Working on an Access 03 db with program front end and data backend. This was
originally a badly designed unnormalized Access 2K db. Prior to conversion I
compacted and repaired outside the db. I then opened it and Access to
converted to 03 format. I made massive changes but 2 of the forms and 3
reports I kept. Before installing on the customers site I did a debug,
compact and repair. At the customers site I use a batch file to copy the
front end to the individual users C:\MSA_Prod\ location. Each user is using
their own new copy of the front end while being connected to the network
backend each time they use the batchfile. 2 hours after installation I get a
call the combo boxes are not working correctly and a query has stopped
working. The combo boxes no longer jump to the first instance of the first
letter entered. The query which uses the Date() function to limit the
results to todays entries shows no entries even though they do exist. Removal
of the Date() from the criteria in the query shows ALL the entries. Including
those entered today.
This smacks of corruption. Debug, compact and repair does not fix.
I used the Export to text file and Import from text file. That did not fix
the problem.
I imported the front end into XP and exported to text and imforted from
text. That seemed to work as the section Namemap was short.
NameMap = Begin
0x0acc0e55
End
On the corrupt ones the NameMap was 20+ lines
The problem is I amd unable to create a new report in a new db and export to
text with out having a large section in the NameMap portion.

How can I create a clean report or are the reports I have created and
exported to text and imported to text in a NEW db safe. The customer is not
happy as I have been attempting to correct this problem for over a week. HELP

 

[Lynn Trapp]

2 things come to mind.

1. If compact and repair is not solving your problem, you might try
importing all objects from the frontend into a new blank database.
2. Check your references to see if any are missing or broken.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Deitzingham]

Did an external compact and repair. Created new db. Imported front end into
it. When Exporting to Text and importing to text
Did a compact and repair on open db. Exported to text.
Created a new db. Copied modules from text to text. Ran code from new
pristine db. Still having problems

 

[ekg]

I have no experience with import and export to text etc, but just have a
couple of "stupid questions"; You use Date() as a criterion, but are all of
the machines synchronised to the correct date ? I would try inserting todays
date manually first, and if that works then the problem is in the
"functionality of the (date) function" Secondly, I think I recall that to
order the list in a combo box you have to ensure that "order by" is effected
in the list query, or if there isn't a list query with "order by" effected
you have to make one - from memory any ordering in the underlying table is
not carried through to the combo box list.

ekg

 

[Deitzingham]

After 5.75 hours on the phone with Microsoft help, it turns out to be
KB-824189
The AutoExpand property may not work when ANSI-92 syntax is enabled and the
Combo Box RowSource does not use DISTINCT values
I turned off SQL Server Compatible Syntax in the Tools-> Options ->
Tables/Queries. To get adequate help I had to navigate through a Microsoft
help person who thought that you could not have a combo box on an unbound
form. The third help desk person did not know what the Date() function was
and when I described it to her asked if it was a square parentheses or a
round one. She then entered it in the query as (Date) and said it hat quotes
around it. After asking for the supervisor and speaking with him he said I
had to allow THEM to deceide they could not help before they would refer me
on. I asked how many incompetent people I had to talk to before they
deceided they could not help? Microsoft did get an answer. I called in at
11:10 CDT and at 4:45 we agreed he would research and call me back. Which he
did by 6:30. Next time I am getting a headset prior to calling Microsoft.