General ledger entry into an xcel upload from access.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am querying on two tables in order to obtain an output for a general ledger
(g/l) reclass.

When I do my query I have 6 columns adjacent to each other. I need to have
the respective matching associated data below the previous one.

My record result from my query is as folllows in a datasheet view for one
example...This is all on the "same row", which I am unable to upload.
R&M Plant 500 / $100 debit)/PO # 100 / R&M Plant 500 / $100 (credit) /
PO# 300.

I would like my query output to be as follows ...
R&M Plant 500 $100 PO # 100
R&M Plant 500 ($100) PO # 300

In a three column format where there are hundreds of g/l entries that need
to be reclassed. It is like I am asking for a carriage return on one match
versus having everything on the same row for that match. I hope I am making
sense of what I am asking.

Thank you for your time and help.
 
ACDenver said:
I am querying on two tables in order to obtain an output for a general ledger
(g/l) reclass.

When I do my query I have 6 columns adjacent to each other. I need to have
the respective matching associated data below the previous one.

My record result from my query is as folllows in a datasheet view for one
example...This is all on the "same row", which I am unable to upload.
R&M Plant 500 / $100 debit)/PO # 100 / R&M Plant 500 / $100 (credit) /
PO# 300.

I would like my query output to be as follows ...
R&M Plant 500 $100 PO # 100
R&M Plant 500 ($100) PO # 300

In a three column format where there are hundreds of g/l entries that need
to be reclassed. It is like I am asking for a carriage return on one match
versus having everything on the same row for that match. I hope I am making
sense of what I am asking.

Thank you for your time and help.
Click to expand...

There may be various ways to do this. My suggestion is to write two
separate Queries on the same tables, one of which returns the 1st 3
fields, the other of which returns the 2nd 3 fields. When you are sure
that each one produces correct values, write a UNION Query to merge both
of these. (You won't be able to do that in Query Design View, but
there's not a lot of SQL necessary to specify the UNION.)

Having written the UNION Query, if you wish to do further filtering or
sorting, you can use Query Design View to define another Query based on
the UNION Query to do the sorting, etc.

-- Vincent Johns <[email protected]>
Please feel free to quote anything I say here.
 
Back
Top