Page 1 of 1

Export amount decimals to MS Access

Posted: 28 Apr 2017, 10:34
by dinis
Hi
Sage 50 V21 - Win 7

I am exporting my GL to MS Access using the Audit_Journal frame, but my amounts come to Access without decimals. As I have too many small transactions, I end up having variances of £10 in some nominals, monthly. How can I include on Access the correct amount coming from Sage? I've linked my database directly to my companies.

Thanks

Re: Export amount decimals to MS Access

Posted: 28 Apr 2017, 11:42
by brucedenney
The ODBC drivers pass values with 2 decimal places.

I have made a 32bit DSN, linked the external table into MS Access using ODBC and as you can see from the screenshot, I have 2 decimal places on the amount in Access
Untitled.png
You talk of the "Frame" assume you mean the table.

You use the term "GL" yet you are actually linking the Audit Trail not the nominal ledger.

Are you using the UK version?

Can you be specific on how you got the table in MS Access, it works fine for me.

Re: Export amount decimals to MS Access

Posted: 28 Apr 2017, 13:57
by dinis
Thanks, Bruce, and forgive my bad English... :)

I do exactly the same thing that you do, but the problem is when Access opens the window "select a unique identifier" . If I choose one field, it brings me decimals, but all other fields are duplicated. e.g. one transaction containing 3 lines with different nominals, will turn up in 3 lines with the same nominals. If I don't select any field, all fields come ok, but amounts come without decimals.
And yes I am using UK version.

If you have any suggestion, I really appreciate.

Re: Export amount decimals to MS Access

Posted: 28 Apr 2017, 14:47
by brucedenney
Are you selecting the transaction no as the unique identifier.?

Re: Export amount decimals to MS Access

Posted: 28 Apr 2017, 14:50
by dinis
Yes, exactly.

Re: Export amount decimals to MS Access

Posted: 02 May 2017, 13:57
by brucedenney
I don't get the same result, mine shows 2 decimal places.

You must be doing something differently or perhaps there is a bug in your version of access or something else.

I can't reproduce your issue so I can't really do much to help.