Alan Enberg
enberga001 at hawaii.rr.com
Sun Mar 2 21:06:59 CST 2008
Darryl, For the past year I've experienced this, managing 3 Access mdbs for one company. Each mdb has about 10-20 users. From what I've read it does seem to be a network issue. Variants I've seen of the '####' are every field replaced with oriental characters, or one or more fields with '#ERROR'. It does seem to occur most often when users are editing memo fields. I find that if you have a numeric PKID (I almost always use auto-number), the key ID will often still be there...but the index will be hosed, so Access doesn't know it's there. So far, I've only had one record at a time get corrupted. If you can determine the key ID, say by looking at the previous and next records, you may be able to restore the individual record instead of the entire database, so you avoid losing all the edits since the last backup. Of course, if the db has many tables with dependent records, this may not be practical. I haven't yet found a solution to this either. Since the index error can make any further record searches fail (essentially stopping all production) and the only solution (I know of) is to get all the users out, compact & repair, delete the offending record(s) then restore them, I wonder how clients with no on-site db manager deal with it. There's doubtless been many threads related to this over the years, but I'd be interested to know how others have dealt with it. Are there any programming methods/trick to avoid this? Alan Enberg -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins Sent: Sunday, March 02, 2008 4:16 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access Table data replaced with ##### in some fields Thanks Debbie. Ok.. That could make sense. These were not just memo fields, but it is over a network which is running somewhat sluggy today and the user in question did have Access fail on them and Access generated a 'compaction error table' in the database. The error wiped out the KeyID fields and a few others and left in about half the field (say 5 out of 10) about 15 #'s and that was it. Naturally not having the KeyID immediately caused a lot of errors. I have a complete backup table which I have used to replace the damaged one with no loss of data so it is a not major issue today. It has shaken the confidence of my new users a bit. urrrgh. If anyone else has had any experience on this I would love to hear your story. regards Darryl. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of delam at zyterra.com Sent: Monday, 3 March 2008 12:52 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access Table data replaced with ##### in some fields I have seen this happen on memo fields. I have been told network issues can cause them. Have not found a better explanation. Debbie Sent via BlackBerry by AT&T -----Original Message----- From: "Darryl Collins" <Darryl.Collins at coles.com.au> Date: Mon, 3 Mar 2008 12:19:45 To:"Access Developers discussion and problem solving"<accessd at databaseadvisors.com> Subject: [AccessD] Access Table data replaced with ##### in some fields Hey There, This looks like some sort of corruption issue. I have a table where two records where the data has been replaced by ####'s. Does anyone know why this may have happened? regards Darryl This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com