Corrupted rows in a table - help needed urgently

  • Thread starter Thread starter Paul Doree
  • Start date Start date
P

Paul Doree

I have recently put together an Access XP database for a client, split into
front and back end. This database works perfectly on my PC at home, but on
the client PC it is generating errors and corrupting rows in a table.

The client is experiencing problems when saving records, getting the error
Invalid Argument. This is then showing as a row in the table with the word
#Error in every field of the row. I have taken a copy of their data and
installed it on my PC, and when I open the table and try to select the
corrupt row I also get the Invalid Argument message, which I have to click
on a number of times to get rid of. The client also has problems with the
standard Access find dialog box, getting a similar error message (but not
always - sometimes it's fine)

I have noticed that the server which the back end DB sits on seems to be
very slow (25 seconds to copy a 2mb file) - could this be a possible cause?

Please help - I can't move the project forward until I resolve this issue.

Paul
 
Paul said:
I have recently put together an Access XP database for a client, split into
front and back end. This database works perfectly on my PC at home, but on
the client PC it is generating errors and corrupting rows in a table.

The client is experiencing problems when saving records, getting the error
Invalid Argument. This is then showing as a row in the table with the word
#Error in every field of the row. I have taken a copy of their data and
installed it on my PC, and when I open the table and try to select the
corrupt row I also get the Invalid Argument message, which I have to click
on a number of times to get rid of. The client also has problems with the
standard Access find dialog box, getting a similar error message (but not
always - sometimes it's fine)

I have noticed that the server which the back end DB sits on seems to be
very slow (25 seconds to copy a 2mb file) - could this be a possible cause?

Please help - I can't move the project forward until I resolve this issue.

Paul
Click to expand...

A couple of things come to mind. Is there plenty of unused space on the
server? Are there different versions of Access involved? I ran into
a problem once with reference library's not being the same. The DAO
Object library was different on the machine generating the errors. I
also think that the references need to be in the same order. I'm only going
from memory here and the solution was given to me from someone else.
IOW I've already told you more than I know :-)

gls858
 
Back
Top