Unsafe Expressions A2K2

[g28dman]

I have recently deployed an application at work [work pcs all running A2K2], built with A2K3 on home computer.

I split the database housing the backend on our server, named server, and using frontends on users pcs.

I am running a VB script that takes information from another linked db on server (so everything would be housed together and not on users pc) this script runs a query converts to xml, opens FTP and uploads the query along with .pdfs to the internet.

I can get it to work from home, no problem. I can get it to work from my pc at work.

But when I try on other pcs it can not find the db (error msg) or opened by another user in exclusive mode, yes I explored this option I dont think this it. 1) Cause the frontend can see the backend and everything works from there. 2) That pc is the only one with an open frontend. 3) When I try opening the actual db from the networked shared folder I get an unsafe expressions alert and can not open. The VB needs to open pull from the 2nd db. Both the backend and 2nd db I get this message.

Can anyone tell me how I can change this, the msg box says its out of trusted network. So I copied and actually opened on local pc, I could open it. Move it back to server and no such luck.

Thanks for any posts, I am having to get this working before I load for other branch offices.

I have googled and searched forum, seems everything is geared towards "sandbox".

 

[Moniker]

That's the "all of our users have convinced us they're idiots security" that is on by default in Access 2003. You need to turn it to Medium or, preferably, Low. It's in Tools->Macros->Security. Your company may have policies in place that mandate something besides Low, but that's the one that assumes you know at least halfway what you are doing. Medium prompts you before opening any DB with macros and/or VBA code in it, and High flat out won't open anything unless it's from a trusted source, which you would have to set up on each computer.

 

[g28dman]

Thanks Moniker for the reply..

My Access 2003 is set to low, the problem is the work pcs are access 2002. After thinking about maybe I could just convert my build down to 02 would that work?

 

[Moniker]

There could be a few issues with that. If you're using ADO, then make sure you're using the 2.5 Library, which is common to both versions. If you're using the 2.8 version in Access 2003 (the default), that won't work in Access 2002 (the default there is 2.7). The ADO reference jumps out as me as I use ADO everywhere. There may be other references that are mismatched as well.

Switching the Access version to 2000 may also do the trick. I don't think there's a "convert from 2003 to 2002" option since they are the same format. (You'll see you can convert to Access 2000 or Access 2002-2003.)

 

[g28dman]

Yep, found that out...Good thing I made a back-up before trying it out. I guess we will just need to break down and upgrade to 03 at work