##### in all table fields (1 Viewer)

[MICHELE]

I tried searching to see if anyone else had this problem but couldn't find anything.

One of the tables in my database has 24 rows with #### filling up all of the fields. I've tried compacting/repairing, deleting the rows and adding them back in from a good table but nothing seems to work. When I copy the table from my backup and look at it from the shared drive on my computer it looks fine but then when I import it to the db with all the other tables those rows change back to #### again.

Does anyone know what's going on and how I can fix it?

 

[KenHigg]

I'm going to make a really silly suggestion; Resize the column width. (???)

 

[MICHELE]

Thank you! I wish that were the problem. I did go in there and try it but the ###'s stay the same size when I resize the columns.

This is so weird - I've never seen anything like it.

 

[KenHigg]

Can you post it (or a sample)?

 

[MICHELE]

Does this help at all? I noticed that not all of the fields do appear messed up. Maybe I can send it as a link.

LSC PROCTR CUSTNUMB CUST STORE#
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############
########## ### ####### ################ ############

 

[KenHigg]

Hum... I was thinkin' more like if you could zip up a sample .mdb and attach it.

 

[MICHELE]

I copied that table into a db and zipped it. Do you want me to email it to you as a copy? I'm not sure how to post it. If you give me your email address i will also work on posting it here too. Thank you!!

 

[KenHigg]

Do: Post Reply->Additional Options->Manage Attachments

 

[MICHELE]

I have 2 copies of the corrupted table. When I deleted the fields that didn't appear to be affected then all of the other fields suddenly looked okay. So then I left the fields in there and only deleted records so that the file wasn't too big. I hope this helps and someone can tell what's wrong.

Please let me know if any other info will help.

Thank you!!!

 

[ScottGem]

Bot sure what hapened here, but the corrupted records seems to have been changed. I suspect that maybe a password input mask was accidentally applied.

 

[mresann]

Since all your data seems to be present, I would go ahead and be safe and create new tables based with the same fields as the old tables. Do the following:

1. Open a new table in design view. Size it to fit half the screen, vertically.
2. Open the corrupted table in design view. Size it to fit the other half so the tables are side by side.
3. Click on one of the records in the original table. Enter Control + A, which will select all the field names and types (and descriptions if they are there). Copy the field name information.
4. Click the first field row in the design view of the new table. Paste all the field names/types onto the rows.
5. Now, your original table does not have a primary key defined. I DO recommend that you have a primary key (or keys for join tables) for every table. Your first field, LSC, contains unique data, therefore it should be used as the primary key field. Highlight this field, and click the little key on the toolbar.
6. Save the table. Open it in datasheet view. Open the original table in datasheet view as well.
7. On the original table, scroll down to the first record that does not contain the ###'s.
8. Select the first row.
9 . Scroll down to the last record.
10. WHILE HOLDING THE SHIFT KEY DOWN, select the last record. All the records from the first record you selected will be highlighted. Right click/copy the data.
11. Select the first record of the new table. Paste the data into the new table.
12. Close the original table. If you want the original name for the table, then change the name of the original table to anything else. Then change the name of the new table to the name of the original table.

You should have no problem with the ### from now on.

 

[MICHELE]

Thank you so much! It seems to be okay now. Any idea why it happened?