I tried this but no luck...

Like so?
G:\SOFTRAK\system\DataDictionaryExporter.exe /ODBC

I tried both but I thought the names were easier to figure out when they were long...
But if i reference the Exported Definition and the ADS Alias Column on the first Worksheet, I guess it makes sense.

Any idea why that table would be empty?

What is the Column "all"vs common do?

Thanks
Yann

Have a look at AdagioODBCv2.chm, Setting Up a DSN
Columns:

Common - Does not show 'hidden' fields in the table and translates coded values. Fields with coded values will have a "_T" suffix added to the field name. 'Translated coded values' should not be used in the WHERE or JOIN clauses of an SQL statement.

For example, WHERE SRTransactions_as80aitm.Type_T="Tax" will not work properly.

Instead, use the All option described below and WHERE SRTransactions_as80aitm.Type="T".

All - Shows the hidden fields and does not translate coded values.

I still haven't figured out why the some tables are empty

See screen shot:
[img]https://drive.google.com/file/d/0B7qAWeNhnmSucnJhY3RvOXJKbUk/view?usp=sharing
[/img]

I'd recommend that you confirm that your APHIST'R data file is greater than 512 bytes. Confirm you are pointing to that data. Then try it without any joins or filters.

It's 11 MB

APHIST'1.DAT is 2.5 MB
APHIST'2.DAT is 3.4 MB

I changed my ODBC DSN to use short names and common Columns...
I created a new crystal report after restarting Crystal (just to make sure it was not a crystal issue). I added the AP81BHST Table and it would not allow me to view any rows that would be inside of it...

if I add the AP81BMTC table, I can see all the columns that exist in the table...

What could be wrong here? Permission?

Thanks
Yann

Hello Yann,

Since you have GridView, do the following:

• Launch GridView pointing to your Account Payable data
• Create a new View from Adagio Payables
• Select the A/P Transaction History Table
• Select some fields from the table
• Don't create a Filter
• See if anything is displayed.

This will tell you whether there is anything in the file.

Then, create a DSN using either the 32 or 64 bit Administrator, depending on the version of Excel you are using. Place "AP*" in the "Table Selection" field and save the DSN. Use long names.

Launch Excel, Choose Data | From other sources. and select your DSN. Choose AP Transaction history from the list of tables. Make sure the table can be loaded into Excel. This will show whether the connection is working properly.

I just went through all these steps with the sample data on my system with Excel 64 bit and everything worked fine.

I then launched Crystal Reports 8.5 and select ODBC as my data source. The Adagio AP one was displayed. I chose the Vendor Master and Transaction History tables to add.

Worked fine:

If you zip the AP data that your DSN or Connection string points to and upload to www.softrak.com/dbr attention Michael I will have a look to make sure that the data is OK. Create a File DSN that is a copy of your System/User DSN and include it with the AP data.

I always suggest that you use Excel | Data | From Other Sources | From Microsoft Query to test your DSN. Looking at the table with Gridview will let you know what data is in the table. ODBC field names are built from Gridview field names with spaces and "special" characters removed.

Hi Andrew,

ok, i found data in the A/P Transaction History via GridView but when I do it through Excel, I get unable to obtain list of tables from the data source.

I'm using 64 bit excel and the 64 bit ODBC the way you suggested it...

Thanks
Yann

Here is another error I'm getting after using the AP* in the table selector...

ODBC Error in Crystal