Text Wrap & Access 2003

[Guest]

I am creating a database for the local United Way office in our county. The
one report is on 11x17 paper but I need to do a text wrap for the column
headings and cannot for the life of me figure out where to do this.

I would appreciate any suggestions. Thanks in advance for your time!

 

[Larry Linson]

I am creating a database for the local United Way
office in our county. The one report is on 11x17
paper but I need to do a text wrap for the column
headings and cannot for the life of me figure out
where to do this.

I would appreciate any suggestions. Thanks in
advance for your time!

Text wrap is the norm in Access Text Boxes and Labels, the two likely
choices for column headings, so perhaps we have some communication problem.
The standard Text Box, or Label, just continues on the next line when you
reach the end of a line -- that's what I consider text wrap to be.

If you could clarify, perhaps someone could assist.

Larry Linson
Microsoft Access MVP

 

[Guest]

Larry,

the heading box (correct term, I guess) for my data grows to the right as I
type in the box or try to put data onto a 2nd line. It's been awhile since
I've used Access, but don't recall coming across this issue previously. I
guess my best example would be like you would do in and Excel data cell -
click on Format, Cells, Alignment, Wrap Text. That's why I'm trying to
accomplish.

 

[Ken Snell \(MVP\)]

To get "text wrap" in a textbox, you must make the textbox more than one
"line" tall. I usually make it 2.5 lines tall so that the wrapping will be
done and so that the user can easily see when there are more than one line
in the textbox.

 

[Ken Snell \(MVP\)]

Oh, and be sure to set ScrollBars property to Yes for the textbox.

 

[Larry Daugherty]

Hi Linda,

Larry L. and ken are giving you solutions that work with Textboxes and
Labels on Forms.

I have the impression that you are trying to make the Headings in
Tables display multi-line. You most definitely can't do that!

You should never be doing you data massaging directly in Access
tables. You should design forms based on the tables and never, ever
require or encourage your users to mess with data in the tables
directly. The word mess is quite deliberate. Even though people
might earnestly do their best to alter only the correct data, mistakes
can and will happen (just as they frequently do in Excel
spreadsheets). One of the compelling reasons for migrating a data
managing application to Access from Excel is that users (and your
application) protected from the risks due to entering data directly
into tables. There are many other compelling reasons for migrating.

To start the design of a Form based on your table: In the
Database|Tables window select the table for which you want a Form and
then, click the AutoForm Wizard Icon. The wizard will step you
through designing a form. Choose things that suit your preferences.
You will probably not get a resulting form that perfectly meets your
needs. Make a few iterations through the wizard making different
choices and viewing the results. Eventually you'll be able to decide
which result is closest to what you want. Give that form a name and
save it. You can then open the Form from the Database|Forms window.
Get into the Design View of the Form and twiddle it more to your
liking. You may want to save several versions of the Form with
appropriately different names that will help you recall what was what
when you created that particular form name.

Welcome to the world of Access.

You won't get very far very fast until you've read a beginner level
book or two ...

There are other Access newsgroups devoted to different functional
areas of the product. Of special interest to beginners with Access
are:
microsoft.public.access.gettingstarted
microsoft.public.access.tables design
also, in your case ... microsoft.public.access.forms

Another resource of value to Access developers of all levels is:

www.mvps.org/access It's full of Access lore and has links out to
other resources. Only a little of what's there makes sense to a
beginner. Even so lurking there is worthwhile because you may not
understand much of a solution until you see that the problem described
is similar to a problem you're experiencing. Then you'll be motivated
to read with keen interest.

Post back with issues.

HTH