Here’s what I got from it.  Browse to the C:\Windows\systwow64 folder and run odbcad32.exe, you should now be able to configure the path to your sage data ase before.  This basically fixed the issue, seems to me that Microsoft have some more work do to.

I belive that this is only an issue with Windows 7 64 bit.  I have installed Windows 7 (64 bit) clean and then installed Sage on top of the clean Windows 7, then Excel 2010 (it was Excel 2007 when I first had the issue) and it worked frist time so if you having issues, a bit drastic but maybe a format reinstall will work.  If you go down the reinstall route ensure that you have a fully tested backup.

UPDATE (16/07/2010):

Put the insturctions for the fix on this post, to save a click.

Would you like a video demo?  If so then please leave a comment telling me so, if I receive enough then I, i’ll do it.

Customer didn’t have any backups, engineer didn’t backup before working on the server!

The thing is he was installing an update to the server (err this is a peer-to-peer Windows XP network, so the server is a dedicated PC holding all the data), which overwrote the database, the setup program didn’t warn him that this was going to happen, of course this isn’t no excuse for not having a backup!

This could of happened to anyone!

No we have to wait for the fall out from this….  to be continued.

Of course this had to happen the week before we (me and my other half that is) fly off to the states to go and get married.