Unable to link to backends on another computer with A2003

[rdemyan via AccessMonster.com]

I just got Access 2003 and have been playing around with it. This whole
macro security thing can be a bit annoying.

Initially, I was able to link to my backends located on a second computer.
Then after I compacted the backends on the other computer and I think I also
tired of the macro security message on Access 2003 and selected to not run
unsafe expressions.

Now I cannot link to the backends on the second computer from the computer
running A2003. I have RWOP queries with all permissions on the backend
tables revoked.

Here's some of the code that I have that does the linking:

'Open the backend db and set the current db
Set wsOPEN = DBEngine.Workspaces(0)
Set dbOPEN = wsOPEN.OpenDatabase(strX)
Set db = CurrentDb()

'Now link the tables
For k = dbOPEN.TableDefs.Count - 1 To 0 Step -1

where strX is the location of the backend file.

At the last line shown, for some reason I'm now seeing

dbOPEN.TableDefs.Count = <Object variable or With block variable not set>

I've never had this problem before using both A2K and A2002. Also, I have
A2K on the second computer where the backends are located. I have no trouble
linking to the backends on that second computer using my application running
in A2K on that second computer.

I have no clue why this is suddenly not working. I guess it must have
something to do with A2003.

Help is greatly appreciated as I am at a loss.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200602/1

[Tom van Stiphout]

On Mon, 27 Feb 2006 06:54:12 GMT, "rdemyan via AccessMonster.com"
<u6836@uwe> wrote:

If you only open MDBs that you trust, and not ones sent to you via
anonymous email, then you can set the macro security (Tools > Macro >
Security) to Low.

-Tom.

I just got Access 2003 and have been playing around with it. This whole
macro security thing can be a bit annoying.

Initially, I was able to link to my backends located on a second computer.
Then after I compacted the backends on the other computer and I think I also
tired of the macro security message on Access 2003 and selected to not run
unsafe expressions.

Now I cannot link to the backends on the second computer from the computer
running A2003. I have RWOP queries with all permissions on the backend
tables revoked.

Here's some of the code that I have that does the linking:

'Open the backend db and set the current db
Set wsOPEN = DBEngine.Workspaces(0)
Set dbOPEN = wsOPEN.OpenDatabase(strX)
Set db = CurrentDb()

'Now link the tables
For k = dbOPEN.TableDefs.Count - 1 To 0 Step -1

where strX is the location of the backend file.

At the last line shown, for some reason I'm now seeing

dbOPEN.TableDefs.Count = <Object variable or With block variable not set>

I've never had this problem before using both A2K and A2002. Also, I have
A2K on the second computer where the backends are located. I have no trouble
linking to the backends on that second computer using my application running
in A2K on that second computer.

I have no clue why this is suddenly not working. I guess it must have
something to do with A2003.

Help is greatly appreciated as I am at a loss.

[rdemyan via AccessMonster.com]

Tom:

I did change the Security level to "Low" and am still having the same problem.
Here's something strange. I made copies of the back-end files (that I'm
having trouble linking to) and put the copies in a new folder on the 2nd
computer. Now, I can link to these copies???!

As far as I can tell there is no difference between the two folders with
regards to security, but I really don't know much at all about folder
security in Windows XP Home Edition.

I just deleted all links in my application. Then I used my custom link
manager to attempt to relink. I pointed to the original file folder on the
2nd machine and now I'm getting an error that says the file path is invalid.
But I used a file dialog window to find it so it must be valid. Then I
switched to the new folder on the 2nd machine with the copies of the backend
files. Linking occurred just fine.

I'd appreciate it if someone could help me try to understand more about what
happened, even if we ultimately can't discover what the real problem is. I'm
not sure what to do now.

Thanks.

Tom van Stiphout wrote:

If you only open MDBs that you trust, and not ones sent to you via
anonymous email, then you can set the macro security (Tools > Macro >
Security) to Low.

-Tom.

I just got Access 2003 and have been playing around with it. This whole
macro security thing can be a bit annoying.

[quoted text clipped - 33 lines]

Help is greatly appreciated as I am at a loss.

--
Message posted via http://www.accessmonster.com

[rdemyan via AccessMonster.com]

Okay. Here's some more information. I took the backend files in the
original folder on the 2nd computer and moved them (not copied) into a new
folder on the 2nd machine. Everything is working fine and A2003 is able to
link.

Something must have happened to that original folder that prevented A2003 on
the 1st computer from accessing the files located in the folder. It's
strange because A2K had no problem linking to the backend files located in
the original folder.

I guess there must be some things I don't understand about Windows XP folders.
If someone could enlighten me or provide me with some resources, I would
greatly appreciate it. Thanks.

rdemyan wrote:

Tom:

I did change the Security level to "Low" and am still having the same problem.

Here's something strange. I made copies of the back-end files (that I'm
having trouble linking to) and put the copies in a new folder on the 2nd
computer. Now, I can link to these copies???!

As far as I can tell there is no difference between the two folders with
regards to security, but I really don't know much at all about folder
security in Windows XP Home Edition.

I just deleted all links in my application. Then I used my custom link
manager to attempt to relink. I pointed to the original file folder on the
2nd machine and now I'm getting an error that says the file path is invalid.
But I used a file dialog window to find it so it must be valid. Then I
switched to the new folder on the 2nd machine with the copies of the backend
files. Linking occurred just fine.

I'd appreciate it if someone could help me try to understand more about what
happened, even if we ultimately can't discover what the real problem is. I'm
not sure what to do now.

Thanks.

If you only open MDBs that you trust, and not ones sent to you via
anonymous email, then you can set the macro security (Tools > Macro >

[quoted text clipped - 7 lines]

Help is greatly appreciated as I am at a loss.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200602/1