This db is a database that tracks sales information, the back end is
SQL, and the front end is plane jane access, 2002, and most of the
clients run the db with the stripped down runtime executable.

I have one user who makes changes to her front end of the sales
database. When I make changes to the database, Which I do all the
time since It's pretty much my database. Okay, when I release an
update, and she overwrites her old one, she loses all her queries and
Reports. She doesn't seem to create macros or tables.

Luckily, all of her objects are prefixed with the name "Cindy."

The program breaks because it can't get read access to Msysobjects in
a database that isn't the current one. I did...

dim fDB as database

set fDb = "C:\accessxp\sales\salesold.mdb"

set rst = db.openrecordset("msysobjects")

and it gets upset right there when it tries to open the other
database's msysobjects saying it doesn't have read permission.

any help?

-Brian P.
Best Data Processing - Holiday, FL

The following code is invalid:

dim fDB as database

set fDb = "C:\accessxp\sales\salesold.mdb"

Try:

Dim fDB as Database
Dim rst As DAO.Database

Set fDb = OpenDatabase("C:\accessxp\sales\salesold.mdb")
Set rst = fDB.OpenRecordset("msysobjects")

Alternatively, you should be able to use:

Dim rst As DAO.Database

Set rst = CurrentDb.OpenRecordset("SELECT * FROM
[;Database=C:\accessxp\sales\salesold.mdb].msysobjects")


"BrianDP" wrote in message
news:1fa26ce3-cfb4-4a32-a6ef-(E-Mail Removed)...

This db is a database that tracks sales information, the back end is
SQL, and the front end is plane jane access, 2002, and most of the
clients run the db with the stripped down runtime executable.

I have one user who makes changes to her front end of the sales
database. When I make changes to the database, Which I do all the
time since It's pretty much my database. Okay, when I release an
update, and she overwrites her old one, she loses all her queries and
Reports. She doesn't seem to create macros or tables.

Luckily, all of her objects are prefixed with the name "Cindy."

The program breaks because it can't get read access to Msysobjects in
a database that isn't the current one. I did...

dim fDB as database

set fDb = "C:\accessxp\sales\salesold.mdb"

set rst = db.openrecordset("msysobjects")

and it gets upset right there when it tries to open the other
database's msysobjects saying it doesn't have read permission.

any help?

-Brian P.
Best Data Processing - Holiday, FL

On Tue, 9 Nov 2010 07:17:08 -0800 (PST), BrianDP <(E-Mail Removed)>
wrote:

>I have one user who makes changes to her front end of the sales
>database. When I make changes to the database, Which I do all the
>time since It's pretty much my database. Okay, when I release an
>update, and she overwrites her old one, she loses all her queries and
>Reports.

Why not give her a frontend containing nothing but links to the
backend database file? Then she can do what she wants in there and
not muck with your Access front end database file.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/