FileCopy Problem in Access 2002

[John Lane]

Has this function been removed in Access 2002, Service
Pack 7? Is anyone using it in Service Pack 7?

 

[Wayne Morgan]

Huh???

The only SP7 I know about for Access 2002 is the Jet4 SP7. The command you want is a VBA
command. What are you attempting to do? There have been some reports of security not
letting certain VBA commands run from within queries (and I believe that most of those
were SP8 related), but FileCopy wouldn't normally be run from within a query.

 

[Guest]

That's what I thought, and these are NOT running within a
query. There is a Knowledge Base article (294698)that
indicates that they are prohibited altoghether, but like
many of these artilces, it's poorly writtens so I can't
tell if it is related to within a query or not. Also, it
seems Sandbox related, but once againt the function is
just a plain old call from within a module. So I was
trying to find out if anyone had trouble running FileCopy
(or anything else in the list for SP7 prohibited functions
under any circumdstance.

I am beginning to suspect the customer is the culprit.
They are "locking down" the "c:" drive, and I suspect they
have monkeyed with the execute permissions on some dll.
Would have any idea what the dll is that supports
FileCopy, and Kill (another one that wont' work), but
Environ works, which is ont he SP7 list.

-----Original Message-----
Huh???

The only SP7 I know about for Access 2002 is the Jet4

SP7. The command you want is a VBA

 

[Wayne Morgan]

They are "locking down" the "c:" drive, and I suspect they

have monkeyed with the execute permissions on some dll.

I've seen that one too many times. It's usually not worth trying to figure out what
they've done is this is the case, reformat and start over.

There have been some reports of the security not working properly with Access 2003 and Jet
4 SP7, upgrading to SP8 tends to relieve those problems. SP8 should be available via
Windows Update. The "sandbox mode" in the help file clearly states that the protection is
for commands called from within a query or entered directly into an event instead of
<Event Procedure>, but that code in a VBA module should not be affected. Before you dig
too deeply, make sure the References haven't gotten messed up. In a code window, go to
Tools|References and make sure the appropriate ones are checked and that none are listed
as Missing.