I urgently need a workaround for the 32bit Office365 problem on a Windows Server 2019 64bit hosted virtual machine.
We had to uninstall O365 64bit on the server and install 32bit version, as the access back-end database to our MS Access app was getting corrupted and the app kept on crashing/hanging and nobody could get any work done.
However, since the downgrade, I have a visual studio .net app that processes emails (microsoft hosted exchange in the cloud), gets and saves the attachments and makes entries in a table in our Access database using oledb provider, which now does not work.
Even after trying every fix, workaround found on every forum covering this long running problem! The .net app is re-compiled for 32bit. I have installed the 32bit 2010 access database engine (even though O365 32bit is installed on the server), but I still
get the ACE.OLEDB error.
What I don't understand is that I can setup a Data Source in visual studio to the backend database (and it uses oledb) and I can see the tables and fields, and even preview the datarows from any table I have setup in the Dataset (it uses myDataSet.Setup.Fill,GetData
() evidently!)
However as soon as the app runs and I try to use the oledb connection.open method, or open a test form which has the dataset, binding sources, table adaptors etc. and a datagrid to show the rows in one of the table, the exception is thrown and I cannot go
any further.
How does the Visual Studio Data Sources IDE get around this problem, but the app cannot at runtime? What is the fix for this urgent problem.
OR....how do I use Microsoft.Exchange.Webservices dll in an MS Access app to get the job done in Access itself then???
Thanks,
MJ
Mike
