Access 2002 doesn't retain column widths

[Ray K]

All of a sudden, all the columns in the db started opening at a fixed
width of 15.6667, with a check appearing in the Standard Width box of
Column Width. If I drag the widths to the way I want them, or use the
Best Fit command, and save the db, the next time I open it the columns
will again revert to a uniform width of 15.6667.

I have two similar databases, each containg names and addresses of high
school classmates. At one time, both retained the widths I set. Only one
now has the problem.

For what it's worth: Under Tools/Options/Advanced, both db's show
default file format as Access 2000, not 2002. And under
Tools/Options/TablesQueries, both db's show default text field size as
40 and default field type as text.

Thanks,

Ray

 

[Ray K]

databases don't have columns. Tables, reports queries and forms have
columns. Where are you having the difficulty?

In the Datasheet view of a Table. That's where the columns revert to
fixed width. Sorry for my careless choice of words.

 

[Ray K]

To the best of my knowledge there is no way of saving the display width
of the fields in a table.

That's not my experience. One of the dabatases has five tables in it.
Only one of them will not retain the column widths I set. I've tried
saving the problem one while holding down Shift, Ctrl and Alt (one at a
time); widths still return to 15.6667.

In the other database, all seven tables in it retains the column widths.

 

[aaron.kempf]

it is saved inside the MDB file.

are you using MDB?

if you're using ADP i would look through the extendedproperties to see
which one was giving you trouble

yet another reason mdb is crap and sql server is the answer to all your
problems

 

[Ray K]

it is saved inside the MDB file.

are you using MDB?

if you're using ADP i would look through the extendedproperties to see
which one was giving you trouble

yet another reason mdb is crap and sql server is the answer to all your
problems

Yes, the database extension is mdb. I can't blame it on that though,
because other tables in the database maintain their widths. Why just one
with a problem, and why should it start acting up just a few days ago
when it's been okay for months?