Re: DLOOKUP VS. COLUMN(N)...

Anything you could send me (demos, apps, links, whatever) will be
GREATLY appreciated! You can use this address:

info@xxxxxxxxxxxxxxxxxx

Thanks, Lupo

On 2 Ott, 00:39, hbinc <j.van.g...@xxxxxxxxx> wrote:
On Oct 1, 11:10 pm, lupo666 <lupo...@xxxxxxxxx> wrote:



HBINC, thank you so much! I'll try it next week when I see my client
again. I only have ACC2000 @ home. I found the linespacing property in
textbox properties in 2000, I think it will be the same in 2007...

Since I never used RTF before, what are the other commands, like \par,
that I could use, eventually? Is there a site I can study?

Thank you again, I'll let u know as soon as I try...

Regards, Lupo

On Oct 1, 10:41 pm, hbinc <j.van.g...@xxxxxxxxx> wrote:

On Oct 1, 6:33 pm, lupo666 <lupo...@xxxxxxxxx> wrote:

Thank you! I am using the column option and it is indeed VERY fast!
Now, I have a problem with a report. Since it is a legal report, it
must be formatted in a specific way, which I have never done before..

I am building some text boxes using as a control source some statis
text and some fields from a query and everything works as supposed to.
The problems are:

I need to have the resulting textbox line spaced as double or 1.5 and
don't know how to do it and
I don't understand why CHR(13) & CHR(10) will not work if I change the
textbox mode to RTF. They will only produce a space, instead.

Actually, I moved the textbox to RTF to try to justify it, since the
"Ripartito" (Reparted, using the Italian version of the software),
does not behave correctly on last lines of paragraphs, pushing them
evenly accross the line, instead of the normal Word-like justified
behauvior...

In the end, I know I am confusing and rambling, sorry, I just need to
be able to line space a textbox on report opening and justify it's
contents in a Word-like way, mind the last line of paragraph...

Thank you for any help u may provide, Lupo

On 24 Set, 00:19, Marshall Barton <marshbar...@xxxxxxxxxx> wrote:

lupo666 wrote:
Hi, I have filled form fields using another combobox field's selection
both with the DLOOKUP function and the id_field.column(n) rowsource
before and they both worked flawlessly...

Searching the Internet, some MVP suggest one, some suggest the other,
MS articles generally point to the DLOOKUP option...

What is the real difference between the two and when one should be
used instead of other?

The .Column(n) property only works for combo and list boxes
when the data you want to display in the control's row
source table/query.  It is immensely faster than using
DLookup so it may be worth adding the field to the row
source query if it is not already there.

If the field you want to display is in an unrelated table,
then DLookup would be useful, especially if you only need to
look up the value a few times.

If the field value you want to display is different for each
record source record, then presumably it can be related to
the form's data in its record source query.  This will
probably be significantly faster than using DLookup.

--
Marsh- Hide quoted text -

- Show quoted text -

Hi Lupo666,

Instead of CHR(13) & CHR(10) you need "\par " to start a new line (in
fact a new paragraph) in RTF.

HBInc.- Hide quoted text -

- Show quoted text -

Hi Lupo666,

It is a quite a lot of work to describe all the commands of RTF.
Instead of that I can send you the specifications of RTF. I picked it
somewhere from internet a long time ago, and I don't remember the site
on this moment.

I developed a couple of routines in VBA using RTF. The most important
- in my opinion - are some routines to make ANY table.
For me this approach is so succesful, that I do not use Access reports
anymore.
These RTF-reports are direct readable, can be send by mail, etc. Using
the same approach but just a little different statements gives me the
possibility to generate HTML-reports.
Moreover, I'm not bound to that one - mostly very complicated - query
as recordsource of the report, but I can mix at will.

Though I still use Access97, I can use among others (pseudo)RTF-
controls, where you can edit the text with the cosmetics that Word
offers.

But...., it is not Access-like!

HBInc.

.

Relevant Pages

  • Re: DLOOKUP VS. COLUMN(N)...
    ... textbox properties in 2000, I think it will be the same in 2007... ... I have a problem with a report. ... textbox mode to RTF. ... MS articles generally point to the DLOOKUP option... ...
    (comp.databases.ms-access)
  • Re: DLOOKUP VS. COLUMN(N)...
    ... I have a problem with a report. ... textbox mode to RTF. ... MS articles generally point to the DLOOKUP option... ... the form's data in its record source query. ...
    (comp.databases.ms-access)
  • Re: DLOOKUP VS. COLUMN(N)...
    ... I have a problem with a report. ... textbox mode to RTF. ... MS articles generally point to the DLOOKUP option... ... the form's data in its record source query. ...
    (comp.databases.ms-access)
  • Re: Summing a calculated control in a report
    ... add tblMainTabs to the report's record source ... In your report, you and then use DomQtr rather than the DLookup(). ... > repeating the calculation and used ...
    (microsoft.public.access.reports)
  • Re: Speed up report.
    ... Is Q_Bookings_OccupDays the record source of your report? ... the client's request) a Total Number of Occupancy Days per Location per ... I'd like to get rid of the DLookUp but I'm not sure how to go about it. ...
    (microsoft.public.access.reports)
Loading