Report

[Gambler]

I have a report and in my report I use HX4 & HX5. I tried to add two queries to my report. One query used PL1 and the other used PL4. So in my report I have HX4, HX5. PL1 query and PL4 query. I made a connection betwen them. Track, Date, Race and Program Number. I keep getting a paceline error when I try and look at my report. Can I joint HX4 & HX5 with queries to make a report?

[MikeDee]

Ed,
The joining of hx4 and hx5 is straight forward. I have never tried to join a hx4 PL5 and hx4 PL1. I'll play aroujnd with it and get back to you

[Rick]

You can do it, the question is how.

Send me a copy of your query and report and I will take a look and play with it.

One way around might me using expressions for the duplicate field names. Something like

rEP2: [PL1]:[rEP]

The idea is there. My puntiation may be wrong, and of course you would replace the PL1 with whatever the table name is.

ricks231@cox.net

[Gambler]

Rick I will send you a copy of my query and report as soon as I can figure out how to send it on AOL. I'm going to try and take what information I use in HX4 and make that a query and the same with H5. Then I will have 4 queries tied together. That is if I can do that. I thank both of you for helping. ed

[Rick]

For me the best way for you to send it is to make a copy of your database, delete all the records, and then run the compact/repair utility.

Then you can either send it as an attachment or zip it and send as an attachment.

It that don't work let me know.

You can always ftp it if you have an ftp program.

[Rick]

Another way, as long as the tables are up to date with the current exporter in HTR2, is to create a new database and import the queries and reports.

You can then email that to me and I can import them into my database to look at.

That will create a smaller file.

[AwolAtHTR]

Fri 2 Jun 2004

hi Gambler,

that sounds like a lot of work for you to share your query design.

consider the following:

A. Enter DESIGN Mode of Access

B. Move important query columns to LEFT of screen so that you can see them.

C. Move Table Join connections so that you can see them

With above, do PRINT SCREEN on your keyboard to capture WHAT YOU SEE

Use PAINT (or tool of your choice) to save the captured screen.

save the captured screen for an attachment to your email.

Oh, side note: IF space is a problem and the color and pictures are NOT important
THEN, when you do the save, change image output color depth or even MONOCHROME.
I use this method and a captured screen in color goes from over 300KB to under 50KB
BUT, that is when I only want the message from the screen and not the pretty pictures!!

If there is a flaw in this method as a Quick-And-Dirty solution for sharing your query,
then, I would appreciate hearing about why this will not work SOMETIMES.

have an interesting day,

AwolAtHTR

[Rick]

AWOL,
It is even quicker and easier to share a query in SQL view. Just copy and paste.

The idea of him sending me what he is working on is so I can play with it and see if I can make it work.

The query should not be the problem. The problem should be in the report and how and what information it is getting from the query.

Granted, some members can look at the pictures and tell what is wrong.

I may be able to do that, but more than likely I will have to get hands on and look at what is doing what in the report.

I ain't looking for a picture. :D