Saving Custom Column Width

134282

N3\/\/b
Local time
Today, 04:07
Joined
Nov 6, 2010
Messages
4
Hello intelligent Access users...

I have an issue I can't seem to solve myself. I found this wonderful forum while attempting to Google a solution to my problem. So without further adieu, here it is...

I've had my Access database for more than six years now; started out with 2003; now it's in 2007. I have four tables and probably close to 100 queries. The tables are defined by serial numbers; the fourth table has six-digit serial numbers (the other tables have smaller serial numbers).

The db was fine the other day, then I opened it (I use it everyday) and the font type and size, as well as the column width, were all messed up for the six-digit serial number table. The other three tables were fine. All queries from the six-digit serial number table are also messed up; but all queries from the other three tables are fine.

I figured out how to get the font type and size back to normal. But nothing I do will save the column width after I've adjusted it. The only way to change the column width is through the Default column width option under the Datasheet tab in the Access Options window. But each column needs to be customized, not at a preset default inch. But every time I set it and save, it goes back to the default after I close the table and reopen it.

Does any of this make sense? I have a headache just typing it.

I'm hoping there's a simple fix for this; I've never had this problem before - and I'm curious as to what caused it in the first place. Mine is a personal computer to which no one has access (lol, no pun intended), so I can't blame this on anyone.

Any direction you can provide would be greatly appreciated. Thanks.
 
Have you saved the changes to the width before closing the table?

Otherwise maybe you have a corrupted table definition. There are a number of things to try

Copy and Paste the table. Check if the copy works properly. If so delete the old one and rename the copy.

Export the table to another database and check if it works there. If so then export it back to the original database.

Create a make table query based on the bad table. If this works then check the field properties are still the same. Make table queries can sometimes make their own decisions about field properties in the destination.

Create a new table from scratch. Create an append query to copy the data from the old table.
 
Okay, I can't copy the table and paste it into Excel.

I copied and pasted the table and the copy saves properly when I customize the column widths. But none of the existing queries are linked to this new copy - which means I would have to re-create all of those queries (dozens!).

I renamed the original table, and then renamed the copy table to the original name of the original table. Now the specific queries pick up the changes made in the table.

But this is a scary move to make not knowing why this happened in the first place.
 
I renamed the original table, and then renamed the copy table to the original name of the original table. Now the specific queries pick up the changes made in the table.

Be aware that if AutoCorrect is turned on the tablename in the queries will automatically change too and still be linked to the original table.

But this is a scary move to make not knowing why this happened in the first place.

Objects get corrupted sometimes, usually when editing but it can happen other times. Always keep regular backups.

Corruption is less likely if you split the tables from the queries, forms and reports into separate databases.
 

Users who are viewing this thread

Back
Top Bottom