[AccessD] PrivDBEngine object no longer works on some XP machines

I think the reason I did not just create a new workspace was because it is a
secure dtaabase with a different system.mdw then the main application. This
secure database is external to the main app and is connected to the main
application through table links. Maybe I misssed something about the WS
object. For some reaosn I thought I didn't have the ability to assign a
system.mdw file. I may also have to loog at ADO as a solution.

John


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Monday, June 07, 2004 11:40 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] PrivDBEngine object no longer works on some XP
machines


Hi John

This object is "non-documented".
Why not just create a new Workspace and open the (backend) database in this?

/gustav


> Anyone run into a problem where the PrivDBEngine objects doesn't work 
> on some XP machines?

> I've been using this routine for years. It allows me to make database 
> changes to secure databases as long as I have the correct system.mdw 
> security file.

> Specs: Written in Access 2000. Resides in an Access 200 MDE library 
> file. Problem occurs runtime or even if PC is already loaded with 
> Access 2000, or XP loaded. Very intermittant. Comes up with an ODBC 
> error/DSN error. Here is a snippet of code:


> It breaks at line 160

> Snippet:


>       Dim dbe As DAO.PrivDBEngine
>       Dim wsp As DAO.Workspace
>       Dim dbEXT_Database As DAO.Database
>       Dim strSecurityFileName As String

> 30    strSecurityFileName="c:\test\system.mdw"

> 90    Set dbe = New PrivDBEngine
> 100   With dbe
> 110        .SystemDB = strSecurityFileName
> 120        .DefaultUser = "USER"
> 130        .DefaultPassword = "PASSWORD"
> 140    End With
> 150    Set wsp = dbe.Workspaces(0)  'systemdb is locked in now

>       'Check the table from the external back end. If There return a 
> true

> 160   Set dbEXT_Database = wsp.OpenDatabase(strDataBaseFileName)

> ALSO, Teery Kreft has done some work in this area. Anyone have her web 
> site or email address?

> John Skolits

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com