sage v23 not a legal oleaut date

Didn't find your answer?

Hi,

We upgraded sage V23 not so long ago, however, when we run reports to export to Excel 2016 we get the following error "not a legal oleaut date".  The PC's and the server both have the correct format for the date and time DD/MM/YYYY.  DOes anybody have any suggestions?

Thanks

Replies (13)

Please login or register to join the discussion.

RLI
By lionofludesch
12th Sep 2017 13:58

Oleaut ?

Sounds like you have the Lithuanian version there.

Thanks (0)
Replying to lionofludesch:
avatar
By tekserv
12th Sep 2017 14:55

Thanks for the reply. What do you mean it could be the Lithuanian version? We ordered an English version through our accountant.

Thanks

Thanks (0)
Replying to tekserv:
RLI
By lionofludesch
12th Sep 2017 14:58

Oleaut is a Lithuanian word.

Thanks (1)
Replying to tekserv:
Man of Kent
By Kent accountant
13th Sep 2017 22:43
Thanks (1)
Replying to lionofludesch:
avatar
By AnderooJames
01st Feb 2018 12:42

It's not oleaut. Its OleAut. A variable name given in the programming. OLE is a type of database connection. Aut will be short for authorisation.

So authorisation of the OLE process to output the data is failing.

The link provided in the reply above explains that the problem is caused by a date, or date-like entry being entered into a database field that is not specified to be a date. The link also suggests a work-around using the Export button and selecting Excel as the required format, rather than using the Excel button directly.

I'm having the same problem today and wasn't having it yesterday. And this solution has worked perfectly for me. And now i have the data into Excel i can figure out what the problematic transaction is and fix it so it stops it reoccurring.

Hope this helps. In a previous life before accounting I was a (not very good) programmer/developer.

Thanks (0)
Replying to AnderooJames:
RLI
By lionofludesch
01st Feb 2018 15:52

So it's not Lithuanian, then.

Thanks (0)
Replying to lionofludesch:
avatar
By AnderooJames
01st Feb 2018 16:06

I'd be very surprised if it was, given the nature of the error - and the translation of the word in Lithuanian. Just a coincidence.

Thanks (0)
By Moonbeam
12th Sep 2017 16:04

Clearly this is another unholy mess made by good old Sage.

You will have to wait for them to write a fix.

Thanks (0)
avatar
By kiwilondon99
13th Sep 2017 21:21

ah ... and i have had to upgrade from a perfectly expensive version to v23 - because i use excel 16

as apparently hitting the send to excel button on v21 to excel16 are not compatible 'offerings'

Thanks (0)
Replying to kiwilondon99:
avatar
By paulwakefield1
14th Sep 2017 08:16

I agree the inability to use later versions of Excel is a right pain. You cannot even use versions that do work if you also have a later Excel version installed.

Workarounds, apart from upgrading Sage, are to export reports, ideally in csv form, or use the ODBC drivers.

If it is a regular requirement, setting up a Power Query will translate the export into a user friendly Excel file painlessly.

Thanks (0)
Replying to paulwakefield1:
avatar
By tekserv
14th Sep 2017 08:43

Sage said I wouldn't have any problems post upgrade to v23 but I had a feeling something wouldn't go right going on past upgrades.

I'll try your suggestions again.

Thanks (0)
Replying to tekserv:
avatar
By kiwilondon99
15th Sep 2017 18:31

got around tothe upgrade today to v23 NOT SIMPLES !!! and when speaking with them they had the audacity to say v24 is around.... who wants a new buggy app - [ and with premium mega expensive maintenance- only finding out these version upgrades are about when you have to speak with them - nice ] Result send to excel 16 works !! at least - now back to the day job having spent so much of it in upgrading.....

Thanks (0)