Another member is having the same problems as listed [url="http://mails.datawatch.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=1;t=000124"]here[/url]. Try some of those suggestions, other than that I don't have anything new to offer.
[size="1"][ March 23, 2006, 05:12 PM: Message edited by: Todd Niemi ][/size]
Hi, Sorry I didn't see the other post.
I'll cross post to that other thread.
This is a problem with nulls and the Microsoft Jet Excel Driver. It was solved in Jet 4 Service Pack 6.
There is a Microsoft KB Article on it Q294410
You will not see this issue with Monarch 6 under Win98SE, ME, 2000 and higher, as we use local dll redirection (only available on these platforms) to point Monarch to a very well tested set of Jet dlls in the Monarch folder.
I have recently upgraded to windows 2000 from NT, with Excel 2000, when I am exporting my table into Excel it is shifting the data across which are usually zeros. But it appears correctly within Monarch. Is this anything to do with the Jet dbase drivers? Any help would be hugely appreciated.
Most of our user's Monarch exposure is through macros I build through Office 97 Excel and Access. So it came to some surprise to me when we updated to Ver 7.01 on one user's computer. The end results of a macro suddenly stop producing the correct figures.
I ran the exact same file on my computer with 7.01 and it ran just fine.
Office 97 + SR2
Windows 98 2nd Ed.
Office 97 + SR2
So I started walking through the macro to see what was up and found that the export from Monarch was shifting the values to the left for some of the rows. That's when I remembered this post!
Since we use Office 97, I didn't think Jet 4.0 would work in this case, so I tried these KB articles for Jet 3.51:
Monarch still shifted the values. :mad:
So I went ahead and tried the link above for Jet 4.0:
Rebooted the machine and lo and behold, Monarch stopped shifting the values!
So the board comes to the rescue again!
Perhaps this thread could be pinned to the top of the thread in case other users find they are having the same problem. It certainly helped me!