[MS_AccessPros] Re: [MSAccessPros] error connecting to database. Cannot open the MS Jet Engine workgroup information file

 

Sue

This started popping up all over the internet forums. It's caused by the latest Office updates that went out on Tuesday. Are you using Kaspersky virus scanner? The advice I've found relates to that scanner. 

The System.mdb (a file size of 0 KB) is created in the application directory. Disable Kaspersky system watcher and remove System.mdb file. 

The above advice is sketchy. I don't know if the poster meant System.MDW or not.

Regards,

Bill Mosca, Founder - MS_Access_Professionals

http://www.thatlldoit.com

Microsoft Office Access MVP

http://mvp.microsoft.com/en-us/mvp/Bill%20Mosca-35852

My nothing-to-do-with-Access blog

http://wrmosca.wordpress.com

---In MS_Access_Professionals@yahoogroups.com, <sue@questor-cp.co.uk> wrote :

I hope someone can help; I am getting this error when attempting to open an application, since moving to Office 2010.

 

This is the application about which I posted a few months ago, when I was trying to generate a complicated query from it. That was successful eventually, but the problem is that the app, developed by someone else, has an Access backend (.mdb, Access 2000 format) and that's the only part I can access.

 

Since installing Office 2010, trying to start the app produces the above error. Any database or backup will open by itself in Access so they are not corrupt. It's obviously not something the developer has come across before either so I thought I would post here in case anyone has any ideas. The standard workgroup file is in %userprofile%/AppData/Microsoft/Access/, but I can't understand why it would matter anyway as – although they are on the same machine – the access dbs are just linked tables.

 

I've tried several fresh installs, and this problem is occurring on 2 machines – the first of which originally had Office 2010 installed a few weeks ago in parallel with 2007, but I uninstalled Office 2007 from it yesterday – after which this issue began. The other is a new machine which had Office 2010 installed from scratch, yesterday.

 

Thanks in advance

 

Sue

__._,_.___

Reply via web post

Reply to sender

Reply to group

Start a New Topic

Messages in this topic (2)

Visit Your Group

• Privacy • Unsubscribe • Terms of Use

.

__,_._,___