[AccessD] Datasheet Subform column width a unhappily resetting

Darryl Collins Darryl.Collins at iag.com.au
Tue Jun 7 22:07:28 CDT 2011


_______________________________________________________________________________________

Note: This e-mail is subject to the disclaimer contained at the bottom of this message.
_______________________________________________________________________________________



Did you find out about this bill?  Curious.

cheers
Darryl

________________________________________
From: accessd-bounces at databaseadvisors.com [accessd-bounces at databaseadvisors.com] On Behalf Of William Benson (VBACreations.Com) [vbacreations at gmail.com]
Sent: Tuesday, 7 June 2011 11:55 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Datasheet Subform column width a unhappily resetting

As additional input... I have decided just to autofit the columns in code
setting columnwidth = -2 ... but if someone knows how come, without that
trick, my columnwidths had been set to some standard uniform width just by
cutting and pasting the controls on the subform... I would appreciate still
to know what I did or failed to do.

-----Original Message-----
From: William Benson (VBACreations.Com) [mailto:vbacreations at gmail.com]
Sent: Monday, June 06, 2011 9:24 PM
To: Access Developers discussion and problem solving
Subject: Datasheet Subform column width a unhappily resetting

Kind Sirs/Madams

I had a database working pretty well, datasheet subforms on a main form. I
had expanded their widths manually, and was happy with everything. I would
shut the form, re-open it, the widths would stay as they were set. Then I
decided to add another field in between the first and second fields on the
subform. This was a little tricky to do because even though I inserted the
field in the correct location in terms of form view, when the form opens in
datasheet view, the field is tacked on at the end. I have in the past
guessed maybe the datasheet view wants to show controls (i.e., columns) in
the order in which they had been added to the form. So what I do to work
around this is I cut all the controls out of that subform in design view and
paste them on a different form's canvas, then cut them and paste them in the
order I want the columns to show in datasheet view. That seems crazy but it
works, because the controls get added to that form's controls collection
anew, and in the right order.

OK, well all of a sudden I do this craziness, and I get partially the result
I want when the main form opens -- in that the datasheet subform does have
the new field and it is in the correct position. BUT ... no matter how many
times I stretch the columns, even SAVING the form before closing it, the
NEXT time I open it, the columns are all the same width. Any ideas why my
columnwidth settings are not being retained? I personally don't know if it
has anything to do with the way the controls were added to the form -- and
in fact I am now on my umpteenth such activity with the same form(s), and
the problem of the columnwidths never showed up until now. But something
changed since I added that field...



--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
_______________________________________________________________________________________

The information transmitted in this message and its attachments (if any) is intended 
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in reliance 
upon this information, by persons or entities other than the intended recipient is 
prohibited.

If you have received this in error, please contact the sender and delete this e-mail 
and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce, disclose or distribute 
the information contained in this e-mail and any attached files, with the permission 
of the sender.

This message has been scanned for viruses.
_______________________________________________________________________________________




More information about the AccessD mailing list