Length of text boxes??? 3

[Paladyr]

I have a report that is cutting off the text of the field it is bound to. Is there a maximum size on text boxes because it doesn't look like you can go into properties and change it. I have tried resizing it to no avail. The field it is bound to is a memo field. I have no clue why Access needs a Memo field either. Thanks!

 

[CosmoKramer]

Paladyr,

Are your sure your query doesn't display your whole memo field? If you use the horizontal scroll bar you are stopped at about 255. Try clicking inside that memo field and use your right arrow key to scroll through the record. I am able to see an entire memo field this way in my query, as well as have it appear on a report.....

 

[BoxHead]

I'm not "informed". I'd have to imagine there's a way to make a table out of your query and base your report on that.

If not, here's an ugly solution that came to mind.

First, decide how large a field you need. (let's say 1000)

Second, Add columns to your query design (one column for each 255 characters)

Third, in Field for Col1, set Expr1: Left(MemoField, 255)
In Col2; Expr2: Mid(MemoField,256,255)
In Col3; Expr3: Mid(MemoField,511,255)
etc...

In your report, set the text source to [Expr1] & [Expr2] & [Expr3] & [Expr4].

That's so ugly, it's hilarious. Good Lord I hope there's a better way.

Sorry,

John

 

[jflo]

If you read in Access help, CanGrow and CanShrink will only take effect when you print a report/form. You won't see changes in desing or in preview mode. If you go in print preview mode you'll see that the text field as actualy grown.

 

[Paladyr]

These reports are truncating the fields AFTER printing as well as before. The way I looked at them in the query was by clicking inside the box and using my arrow to scroll right until it moved me to the next box, signalling the end of the string. I am 100% positive the query is truncating the field.

Boxhead, I like your idea, I'll give it a whirl since nothing else seems to work .

 

[Paladyr]

Could it be possible that since this database was converted from an access 97 database to a 2000, it is causing all these problems (i have had other problems that I posted today)???

 

[Databaseguy]

Well, I'm Stumped. I've got a table with all the SQL statements in my DB. I just made a quick query, and some are very long. (The longet being 2683 characters).

I set the can grow and can shrink on the report, and all of the statements printed.... Tyrone Lumley
augerinn@gte.net

http://server105.hypermart.net/databaseguy

 

[milesada]

i have an idea... check the can shrink/grow properties for the section of the report (group header/footer or details, wherever these fields are printing...

a.

 

[Paladyr]

So am I, i guess I will just count on it going away when I get around to redesigning this hunk of junk in VB. Thanks for all your help! Also, this is the same database, another weird problem that makes me think something was lost in the conversion:

thread181-144800

 

[tempclerk]

If you want to give the DLookup another go, try putting your memo field name in square brackets and using the complete reference to your Start Date and Specialist fields (Tables![Table Name]![Field Name]). That's one thing that bugs me about the domain aggregate functions - the syntax is far too confusing.

 

[Paladyr]

I'll give it a whirl tomorrow, thanks for the help!