Vielen Dank Olly.
I looked in the audit trail now further to your suggestion but nothing changed.
Also, my own .dbfs corrupted after I tried to help him. Its as if i corrupted something on my pc by using his models and trying to export. I was just trying to see what the problem was as I thought initially it was a model error and I could help to fix it.
Now my own models/tables also don't export to .dbf and I didn't change anything in the models. They worked the week before.
Also, when I try to open a .dbf file to look at it in Monarch..file....open database...I get error OLE DB Internal Error: Unexpected error from external database driver (8458).
This must be connected to the export error.
I have also created a new model and table and tried to export that to .dbf, assuming the original is somehow corrupt and it doesn't work either, same error.
Try the custom search: http://www.google.com/cse/home?cx=017979669301925061066:c4v8ksw-llg[/url] as the forum software doesn't index three letter words like DBF
DBF seems fussy about field names longer than 10 characters, or with spaces in - does that help at all?
It didn't work.
I installed the fix from the link you sent:
but it didn't work.
There was nothing else there that helped.
I created new models with small field names and no spaces etc but the exports have worked for years and now suddenly they won't.
I'm getting desperate now. I don't think we can ever fix this.:(
[SIZE=3]Jet is used by many other applications, so it is more thanpossible that a totally unrelated application update has updated part of the MicrosoftJet data base engine that it uses, but left other parts alone. We used to see this problem often withAutoroute updates for example – and that was a Microsoft application at the time![/SIZE][/FONT]
[SIZE=3]Please visit /SIZE[/FONT][URL="http://support.microsoft.com/kb/239114"][FONT=Calibri][SIZE=3][COLOR=#0000ff]http://support.microsoft.com/kb/239114[/COLOR][/SIZE][/FONT][/URL][FONT=Calibri][SIZE=3]to make sure your Jet Database is looking OK. Unfortunately, Windows update will not always keep this in tip topcondition as it doesn’t always detect the fact that it is mismatched. Andsometimes, Jet will report it is OK, when close examination of the DLL versionswill reveal that it is not.[/SIZE][/FONT]
[SIZE=3]As an emergency fix, you may be able to export the data by going into "options->Export and Clipboard" and selecting one of the older file versions from the drop down. This may impact performance and you will lose flexibility in the formatting opions, but should let you get the data out.[/SIZE][/FONT]
Steve (and Olly)
Thank you so much for your advice, very much appreciated.
I have followed Steve's suggestions to the letter, the IT department updated all the Jet settings (hence the delay in response) and still no joy. We are getting the same error message.
I also tried going into Export and Clipboard and choosing older file versions.
I think I am doomed to using excel exports forever now.
I tried to do the exports on another colleagues machine with old models and files so that there could be no corruption. This colleague has a license but never uses it. I got the same error so it does suggest a network or systems change that is affecting us all.
I will ask IT to update as many Windows packages etc, maybe we will strike lucky.
Any other suggestions are welcome, I do appreciate the time you are taking to help me and the enthusiasm is great, thanks.
We had this problem recently (Jan-2018) on Monarch v7.02 following Patches to Windows 7 and export to Excel 2010 fails...
Workaround Fix (in our case):
1. From the Option Menu > Select "Export and Clipboard"
2. Set the XLS files drop down to "Excel 97+"
3. Tick "Apply formatting"option
4. Click OK..
Strange that a patch would reset this option - took me a while to figure it out too!!!