Front End seems to loose track of Data when Compacting

  • Thread starter Thread starter Carlos Martinez
  • Start date Start date
C

Carlos Martinez

Hi,

I did a Compact/Repair DB on the Back End of a split database. After that,
I found that the data looked strange in the front end (basically, some fields
in forms were showing international characters that were not supposed to be
there), and other minor nuances.

The problem, while present on some of my users client machines, began
"repairing itself" as the day went by. I had a test area where I managed to
reproduce it, and I noticed that the behavior seemed to go away as soon as I
did something that refreshed the data in the front end.

All through my analysis the back end data looked fine.

Should I have done any sort of "link refresh" on the front end after the
Back End Compact/Repair operation?
 
On Tue, 26 Jan 2010 15:09:01 -0800, Carlos Martinez <Carlos
Should I have done any sort of "link refresh" on the front end after the
Back End Compact/Repair operation?
Click to expand...

It shouldn't be necessary but it can't hurt. TURN OFF Name Autocorrect before
doing this (heck, turn it off and leave it off, it's buggy and dangerous!)
Then try deleting all the table links from the frontend; compact; and use
File... Get External Data... Link to reconnect them.
 
Thanks for your reply, John. I will do just that the next time that I
perform a compact/repair on the Back End; the "strange behavior" continues to
spread and disappear from my customer's clients, so I feel like I am chasing
a squirrel.

Those FEs that have "repaired themselves" are no longer subject to any
issues...

That is what leads me to believe that the problem lies somewhere in the
relationship between the front end and the back end. All throughout the data
in the back end has withstood careful analysis...

Thanks again!

Carlos
 
Thanks for your reply, John. I will do just that the next time that I
perform a compact/repair on the Back End; the "strange behavior" continues to
spread and disappear from my customer's clients, so I feel like I am chasing
a squirrel.

Those FEs that have "repaired themselves" are no longer subject to any
issues...

That is what leads me to believe that the problem lies somewhere in the
relationship between the front end and the back end. All throughout the data
in the back end has withstood careful analysis...
Click to expand...

I'm not sure this is relevant, but in my experience you can get really wierd
things happening if you make ANY design changes to a table in the backend.
Relinking will not cure these wierd things and can even aggravate them; I've
taken to routinely deleting all links, compacting, and creating new links if I
make *any* structural change to a backend table.
 
Back
Top