B
Brian Smither
Here's a complete mystery...
I was using Access 2003 to open and manage an MDB located on a remote
server. In the datasheet view of tables and queries, I've adjusted the
width of the various columns to that which I am comfortable. All OK and
good. The geometries persist.
Then I upsize the table into SQL Server 2005 Express - still on the remote
server. The SSMSE shows the columns all having an equal width. I can adjust
each individual column's width, but the geometries do not persist.
So, I decide to have Access link to SSE - the method chosen was ADP. I
create a brand new .adp file and have it connect to the requisit SSE
database that was just created. New ADP, new SSE tables, new connection...
Guess what? The geometries of the columns (as set by the old MDB table)
manifest themselves in the datasheet view of the (new) SSE table! How does
that happen? And why can't SSMSE honor those geometries?
I was using Access 2003 to open and manage an MDB located on a remote
server. In the datasheet view of tables and queries, I've adjusted the
width of the various columns to that which I am comfortable. All OK and
good. The geometries persist.
Then I upsize the table into SQL Server 2005 Express - still on the remote
server. The SSMSE shows the columns all having an equal width. I can adjust
each individual column's width, but the geometries do not persist.
So, I decide to have Access link to SSE - the method chosen was ADP. I
create a brand new .adp file and have it connect to the requisit SSE
database that was just created. New ADP, new SSE tables, new connection...
Guess what? The geometries of the columns (as set by the old MDB table)
manifest themselves in the datasheet view of the (new) SSE table! How does
that happen? And why can't SSMSE honor those geometries?