Re: text box truncating on access group header

I don't have any other ideas at this time. I cannot reproduce the problem
with an example setup here, so the only alternative is to see firsthand what
is happening in your database. I've checked with another MVP who has
experience with Oracle tables, and he doesn't believe that they would be the
problem.

Can you extract some examples of the data to a table in the database file,
change the queries to use the local tables with the example data, and
provide that database for my "look-see"?

--

Ken Snell
<MS ACCESS MVP>



"jeremyj54" <jeremyj54@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6388FA7D-C24C-44DC-BDD7-190C228E5B2B@xxxxxxxxxxxxxxxx
Im not sure if sending the database to you would do any good because it is
just reporting on linked tables from an oracle database you wouldn't have
any
of the data. I have tryed a couple of things that are kind of interesting
to
me, I made a column in my query and just made it an expression
"aaaaaaaaaaaaaaaabbbbbbbcccccccc etc." and put it in the report and it
truncated at 255 then I put an unbound textbox on the report and made the
controlsource ="zzzzzzzzzzzzzzzzzzzzzzzwwwwwwwwwwwwwwwxxxxxx etc." and it
did
not truncate. Any thoughts I am losing my mind with this one.

"Ken Snell (MVP)" wrote:

Use of First aggregate function is recommended in order to avoid having
to
put a memo field into the GROUP BY clause, so that does have its uses.
However, for your report's needs, you should be able to use a normal
select
query, which will not truncate a memo field.

Now, there is one other item that can cause truncation when you export a
query, and that is the use of the RAW2STR function. When you have a
user-defined function in a query, memo fields (even if not involved in
the
function) are truncated if you try to export that query. However, because
you're not exporting here, I don't see that as the problem.

I also assume, based on your initial post about truncation not occurring
in
the detail section, that the RAW2STR function is not causing truncation
of
the string itself.

I still am thinking there is something in the Group Header section's
properties that is causing this truncation, but I am at a loss to
speculate
further. Would you be wiilling to email me a copy of the database that
would
demonstrate the problem? I may be able to better spot the problem if I
can
dive into it. If yes, you'll find an email for me at this website:
www.cadellsoftare.org

--

Ken Snell
<MS ACCESS MVP>



< snipped >


.

Relevant Pages

  • Re: Union All query truncating
    ... The truncation occurs if I just run the query, ... and it is still truncating on the query. ... "Ken Snell " wrote: ... <MS ACCESS MVP> ...
    (microsoft.public.access.reports)
  • Re: Union All query truncating
    ... you have found another example of string truncation in ACCESS. ... Then you use a UNION ALL query to ... Ken Snell ... <MS ACCESS MVP> ...
    (microsoft.public.access.reports)
  • Re: Confused about log size after running Backup/Maintenance
    ... Transaction Log file (the *.ldf) would not be truncated by itself. ... To truncate the passive virtual logs in your Transaction Log file, you should back it up using Transaction Log Backup. ... As much as you perform operations against your database, this file will grow that much. ... And you may want to take a look at Tibor's article about this Truncation and Shirinkage. ...
    (microsoft.public.sqlserver.setup)
  • Re: text box truncating on access group header
    ... query, and that is the use of the RAW2STR function. ... based on your initial post about truncation not occurring in ... <MS ACCESS MVP> ... "Ken Snell " wrote: ...
    (microsoft.public.access.reports)
  • Re: text box truncating on access group header
    ... "Ken Snell " wrote: ... query, which will not truncate a memo field. ... based on your initial post about truncation not occurring in ... <MS ACCESS MVP> ...
    (microsoft.public.access.reports)