Split Form with datasheet word wrap

[data808]

I have a split form that I use the form header with some buttons for the user to navigate through the database. The detail part of the form is not visible. So when the user opens this form up it shows the header with the buttons at the top and then below it is the datasheet. I would like to know if there is some kind of word wrap feature for the datasheet. The datasheet has fields consists of regular short text, long text, and one drop down list or combo box. The long text are the ones that contain a large amount of data and the row height is not large enough to see all of it. I would like this datasheet to increase the row height automatically so I don't have to change it myself manually. I thought the property that would handle this is the "Can Grow" and "Can Shrink" properties but I could not get it to work. Anyone know how to solve my problem?



Thanks.

[June7]

I don't know why those properties even show for textboxes on form. They only seem to work on reports.

Why are you using split form if not displaying record data in the top half? Use a regular form set for Continuous View. Put buttons in the form header. Arrange and size controls as you see fit. Textboxes on form will then show vertical scroll bar.

[Missinglinq]

...I don't know why those properties even show for textboxes on form. They only seem to work on reports...

Actually, they work on Forms but only when you are printing a Form! And since we all know that printing a Form is...well...considered bad 'form' (sorry, couldn't help myself!) we return to the question of why those properties show on Forms! I, myself, have always wondered why they allow a Form to be printed at all!

Linq ;0)>

[June7]

That does clear up mystery. I know, printing forms are bad. But I have one situation concerning legacy data. I needed to make data available for screen and print but didn't feel like building 22 more reports that wouldn't be used often, if ever. So I built the forms to serve for those rare occasions. They aren't as pretty as my new reports but they work.

[data808]

Forgot about Continuous forms. Thanks. I'll try it out and get back to you.

[Missinglinq]

...I know, printing forms are bad. But I have one situation concerning legacy data. I needed to make data available for screen and print but didn't feel like building 22 more reports that wouldn't be used often, if ever. So I built the forms to serve for those rare occasions...

Any rule that doesn't allow for exceptions shouldn't be a rule!