Error 3275 in Access 2000 when exporting to Excel using a query in a VB program

[codelines]

I have a program using an Access 2000 database and I export data to Excel using a query in this format:
SELECT filed1, field2, field3 INTO [EXCEL 8.0;DATABASE=C:\MyFolder;].[MyWorkSheetName] From [MS Access;Database=C:\MyFolder\MyDatabase.mdb].TableName

From yesterday, I have received the error "3275 - Unexpected error from external database driver" evey time I try to expot data. Does somebody know if a recent Access update have caused this error?



Thanks

[ranman256]

try
docmd.TransferSpreadsheet acExport ,acSpreadsheetTypeExcel12,vQry,vFile,true,vSheetNa me

[codelines]

Thanks, ranman256, but I'm not using VBA, my program is in Visual Basic. But if I can not find a solution, I will try using the Access Application object to export with DoCmd. In this case, my users will need to install other Access components.

[aytee111]

You can also use a macro instead of VBA.

[Micron]

I have a program using an Access 2000

You wrote the program using VB6 or VB.Net and it is mining Access for data? To me, export Access data to Excel means the code execution is on the Access side. Import to Excel means the code execution is on the Excel side. Using code in either of these applications highly suggests the code is VBA not VB. While I would believe you if you said you referenced the VB library so you could write VB code in a VBA environment, to do so just wouldn't make a whole lot of sense.

[codelines]

I wrote my program using VB6 and the object Database has a method Execute that execute an sql query in a text like the one I posted above and that sql query exports data to Excel 8.0 format.

Now I discovered that the problem was caused by the last Office updates of 10/10/2017. A customer of mine have used a restore point before 10/10/2017 and all worked fine.

[Micron]

I had a feeling that the Excel version being used in the select statement might be an issue but there are so many possibilities for this issue that I didn't want to start something.- especially since I thought this was operating in your usual environment and would have mentioned system upgrades as you would know about them. Also ignored the "filed1" which I presume is a typo.

[codelines]

Micron, the code has worked in more then 2000 customers for years. Now, after the Office updates the error has occured.

[Micron]

Because their Excel version isn't 8.0 any more right? They probably end up with 14 or higher after the upgrade. That would cause it.

[codelines]

No, Excel 8.0 is from 20 years ago or more and some of my customers use Excel of the most recent Office edition and my query was running ok there till 10/10/2017.

[MzTinaFL]

Codelines - I'm experiencing the same problem with importing .xls files into an Access 2000 program. Our latest update seems to be the culprit. When you mention restore back to previous point; do you mean you uninstalled the update for excel or did you uninstall all office updates? (note: I have Office 2016, Access 2003).

[codelines]

A customer of mine has restored only the state before 10/10/2017 and all goes right. So, the problem was the latest updates. If they affect imports too I don't know as my problem is with exportation. I have worked around the problem using the Excel object model to create a generic procedure to export data.

[orange]

Her e is a link re patches for Oct 10 2017
https://www.lifewire.com/patch-tuesday-2625783

[codelines]

What this has to do with our problem? It's only the announce of the updates that are the cause of it.

[orange]

Or this one from M$oft
https://support.microsoft.com/en-ca/...crosoft-office