dmDriverExtra error

[stuart_adair]

Hello all,

I have 3 Access databases running on a server. I've just started to get this message "dmDriverExtra too large" when I try to create a new report or query.
Rest of the time the databases work fine.

Any ideas ?

Thanks
Stu

 

[stuart_adair]

No replies - Does that mean I've beaten the clever people

 

[boblarson]

Haven't ever heard of that before, but are you using something named dmDriverExtra in code somewhere. I did a Google Search and found that it was associated with some code for Word (in the ones I found) and so if you are using it, how are you declaring it?

 

[stuart_adair]

No I've never heard of it before and adding any sort of code is way over my 'cleverness rating'. As far as I know we havent made any changes to the servers so I'm really struggling.

 

[boblarson]

Are these databases that are having a problem split? If not, they need to be. If they are, are the frontends being run from the server or from a copy on each user's machine? If from the server, that again is a problem. It shouldn't be.

If not split, it could be corruption causing the problem (it could be corruption with a split db too but is less likely unless the frontend is being run from the server and then it is as likely as a non-split database).

 

[stuart_adair]

Hi Bob,
No they aren't split and have been running quite happily since 2007 without any issues. The database's regulaly get trimmed to optimise the data so the file size's arent large. I'm just wondering if some IT 'Oik' has done something with the servers without telling me

 

[boblarson]

Hi Bob,
No they aren't split and have been running quite happily since 2007 without any issues.

That may be, but as I say - it isn't a matter of IF it will corrupt, but WHEN. In your case it took 4 years. Multi-user Access databases should be split - no if's, and's, or but's about it. You increase your chances of corruption and losing the whole thing 10 fold if it isn't split. In your case you just happen to be lucky enough that playing Russian Roulette with your database hasn't resulted in a loaded chamber coming around and killing it.

The database's regulaly get trimmed to optimise the data so the file size's arent large.

It matters not the file size. If a single network disruption occurs, no matter how slight, while a user is in your database, it can totally destroy it. I tell you fact and if you choose to ignore that, so be it, but you can't say you haven't been warned.

I'm just wondering if some IT 'Oik' has done something with the servers without telling me

Possible

But trying to create a report or form in Access (are you really logging into the server and doing this or using Access on your machine but trying to do design work over the network?) and it throwing the error, it could be that there is something wrong with the Access installation, or it could be that there is something wrong with the Access databases themselves. Can you create a new database and then create a form or report without it doing that?

 

[stuart_adair]

All,

My problem was eventually solved by a clever IT person at work. I've pasted what he told me below incase anyone else has an issue...

"The issue was that the default printer was set to Thin Print Output Gateway which isnt compatible with the new virtualised terminal servers."

The solution was simply to change my default printer.

Who says all IT support people are useless

 

[boblarson]

Thanks for posting back with the solution. I'll admit it was quite a puzzler.