ULS and Converting Down

[Guest]

It seems that the Citrix environment that my company uses offers some challenges

..mdb files default to Access 97. So, I made a shortcut to the mapped drive in Citrix where Access 2000 resides, including the secure.mdw workgroup and my database

Now, I'm learning that the mapped drive for the application is not the same for all of my users. And they aren't sharp enough to know how to make a shortcut for themselves and make the necessary mods (in addition, even if I use the computer ID where the applications are stored, they are hidden, and I cannot find the directories necessary)

That said, I need to downgrade my database to 97. I do this with great hesitation. I have AllowBypasKey to false, ULS for 40 users, split database. I'm in 2000 now. Is this a big problem, or should it be fairly uncomplicated

Thank you
Derek

 

[Joan Wild]

Converting down to 97 shouldn't be a huge problem, unless you've used
features in 2000 that didn't exist in 97.

The fact that it's secured, I believe that if you convert the resulting
database is unsecured - not sure. I would suggest you experiment on a copy
of your mdb (of course).

Have a look at DbUtilities 1.0 at
http://www.daiglenet.com/MSAccess.htm
You can use this to script out the permissions.

Try converting to 97 and see if the permissions stick. If not then you have
the above utility to apply them once they're in 97.

--
Joan Wild
Microsoft Access MVP

It seems that the Citrix environment that my company uses offers some challenges.

.mdb files default to Access 97. So, I made a shortcut to the mapped

drive in Citrix where Access 2000 resides, including the secure.mdw
workgroup and my database.

Now, I'm learning that the mapped drive for the application is not the

same for all of my users. And they aren't sharp enough to know how to make
a shortcut for themselves and make the necessary mods (in addition, even if
I use the computer ID where the applications are stored, they are hidden,
and I cannot find the directories necessary).

That said, I need to downgrade my database to 97. I do this with great

hesitation. I have AllowBypasKey to false, ULS for 40 users, split
database. I'm in 2000 now. Is this a big problem, or should it be fairly
uncomplicated?

 

[Guest]

I'm kinda not all together today. I've downloaded the dbutilities97 and don't exactly see how it runs.

I have learned that I think I need to desecure the database before downgrading. Not a big problem.

Do I have to convert the front AND back ends?

Thanks!
Derek

----- Joan Wild wrote: -----

Converting down to 97 shouldn't be a huge problem, unless you've used
features in 2000 that didn't exist in 97.

The fact that it's secured, I believe that if you convert the resulting
database is unsecured - not sure. I would suggest you experiment on a copy
of your mdb (of course).

Have a look at DbUtilities 1.0 at
http://www.daiglenet.com/MSAccess.htm
You can use this to script out the permissions.

Try converting to 97 and see if the permissions stick. If not then you have
the above utility to apply them once they're in 97.

--
Joan Wild
Microsoft Access MVP

It seems that the Citrix environment that my company uses offers some challenges.

drive in Citrix where Access 2000 resides, including the secure.mdw
workgroup and my database.same for all of my users. And they aren't sharp enough to know how to make
a shortcut for themselves and make the necessary mods (in addition, even if
I use the computer ID where the applications are stored, they are hidden,
and I cannot find the directories necessary).hesitation. I have AllowBypasKey to false, ULS for 40 users, split
database. I'm in 2000 now. Is this a big problem, or should it be fairly
uncomplicated?

 

[Guest]

I've got the conversion to 97 done. But not the permissions/users taken care of. I have created a new mdw file with the workgroup administrator. Yet, when I open my unsecured database with my shortcut, pointing to my new mdw file, the Security Wizard points to the system.mdw file. And I cannot get to Access 97 without being in the Citrix environment

And I am working on a backup... thanks for the reminder
Dere

----- Joan Wild wrote: ----

Converting down to 97 shouldn't be a huge problem, unless you've use
features in 2000 that didn't exist in 97

The fact that it's secured, I believe that if you convert the resultin
database is unsecured - not sure. I would suggest you experiment on a cop
of your mdb (of course)

Have a look at DbUtilities 1.0 a
http://www.daiglenet.com/MSAccess.ht
You can use this to script out the permissions

Try converting to 97 and see if the permissions stick. If not then you hav
the above utility to apply them once they're in 97

--
Joan Wil
Microsoft Access MV

It seems that the Citrix environment that my company uses offers som challenges

drive in Citrix where Access 2000 resides, including the secure.md
workgroup and my databasesame for all of my users. And they aren't sharp enough to know how to mak
a shortcut for themselves and make the necessary mods (in addition, even i
I use the computer ID where the applications are stored, they are hidden
and I cannot find the directories necessary)hesitation. I have AllowBypasKey to false, ULS for 40 users, spli
database. I'm in 2000 now. Is this a big problem, or should it be fairl
uncomplicated

 

[Joan Wild]

Hi Derek,

You have a secure 2000 mdb, right? Therefore you should download
dbutilities 1.0 which is for version 2000.

Open your 2000 mdb and import all the objects from dbUtilities. Go to the
debug window (Ctrl-G). Type

DumpPermissions()

The table $tblPermissions will list the permissions - keep this table.

You could then unsecure the 2000 mdb, following the steps in the FAQ.

Then convert to 97, and resecure it there using the same group and user
names that you had in the 2000 version.

Then to reapply the permissions, you would run
LoadPermissions() in the debug window.


--
Joan Wild
Microsoft Access MVP

I'm kinda not all together today. I've downloaded the dbutilities97 and don't exactly see how it runs.

I have learned that I think I need to desecure the database before

downgrading. Not a big problem.

 

[Guest]

I'm learning, too, that even once I get to the Secure 97 Database file, I don't have the ability to make a good shortcut, since the drive mapping is different for the different facility locations. While my executable MSACCESS.exe file is on R:, that's not where it is in Tacoma, Washington, or in Syracuse, NY. And it doesn't appear that I can just have a shortcut that points to the database and workgroup without the executable... The database opens, but that's just due to filetype association. The workgroup applied is the one that I have joined, not the one designated in the /wrkgrp argument

Any other ideas would be really appreciated

Thank you
Dere


----- Joan Wild wrote: ----

Hi Derek

You have a secure 2000 mdb, right? Therefore you should downloa
dbutilities 1.0 which is for version 2000

Open your 2000 mdb and import all the objects from dbUtilities. Go to th
debug window (Ctrl-G). Typ

DumpPermissions(

The table $tblPermissions will list the permissions - keep this table

You could then unsecure the 2000 mdb, following the steps in the FAQ

Then convert to 97, and resecure it there using the same group and use
names that you had in the 2000 version

Then to reapply the permissions, you would ru
LoadPermissions() in the debug window


--
Joan Wil
Microsoft Access MV

I'm kinda not all together today. I've downloaded the dbutilities97 an don't exactly see how it runs

I have learned that I think I need to desecure the database befor downgrading. Not a big problem
Do I have to convert the front AND back ends
Thanks Dere
----- Joan Wild wrote: ----
Converting down to 97 shouldn't be a huge problem, unless you've use

features in 2000 that didn't exist in 97

The fact that it's secured, I believe that if you convert th

resultin
database is unsecured - not sure. I would suggest you experiment o a cop
of your mdb (of course)

Have a look at DbUtilities 1.0 a

http://www.daiglenet.com/MSAccess.ht
You can use this to script out the permissions

Try converting to 97 and see if the permissions stick. If not the

you hav
the above utility to apply them once they're in 97

--

Joan Wil
Microsoft Access MV

 

[Joan Wild]

In order to use a /wrkgrp switch, you must include the path to msaccess.exe
or the switch will be ignored and you will be using system.mdw.

I wouldn't be doing all this over Citrix. Can't you copy the mdb to your
local machine, set up everything and then copy it back?

--
Joan Wild
Microsoft Access MVP

I'm learning, too, that even once I get to the Secure 97 Database file, I

don't have the ability to make a good shortcut, since the drive mapping is
different for the different facility locations. While my executable
MSACCESS.exe file is on R:, that's not where it is in Tacoma, Washington, or
in Syracuse, NY. And it doesn't appear that I can just have a shortcut that
points to the database and workgroup without the executable... The database
opens, but that's just due to filetype association. The workgroup applied
is the one that I have joined, not the one designated in the /wrkgrp
argument.

Any other ideas would be really appreciated.

Thank you!
Derek


----- Joan Wild wrote: -----

Hi Derek,

You have a secure 2000 mdb, right? Therefore you should download
dbutilities 1.0 which is for version 2000.

Open your 2000 mdb and import all the objects from dbUtilities. Go to the
debug window (Ctrl-G). Type

DumpPermissions()

The table $tblPermissions will list the permissions - keep this table.

You could then unsecure the 2000 mdb, following the steps in the FAQ.

Then convert to 97, and resecure it there using the same group and user
names that you had in the 2000 version.

Then to reapply the permissions, you would run
LoadPermissions() in the debug window.


--
Joan Wild
Microsoft Access MVP

I'm kinda not all together today. I've downloaded the

dbutilities97 and
don't exactly see how it runs.

you've used
features in 2000 that didn't exist in 97. resulting
database is unsecured - not sure. I would suggest you

experiment on
a copy

of your mdb (of course).
http://www.daiglenet.com/MSAccess.htm
You can use this to script out the permissions.

not then
you have

the above utility to apply them once they're in 97.

--

Joan Wild
Microsoft Access MVP

 

[Guest]

In theory, that's what my goal has been to do. However, my PC does not have Access 97. So, I need to set up everything and then convert to 97, implementing a new MDW file - I have learned that the MDW cannot be converted 97; I get a specific dialog message telling me that

The advantage to doing it on Citrix is that my users can test it out faster, so I don't have to keep putting it up and taking it down

About the only thing I like Citrix for is that I can get email when I go to another site with it - and I don't need to find an analog line for my laptop. Stupid token-ring and subnets..

Dere

----- Joan Wild wrote: ----

In order to use a /wrkgrp switch, you must include the path to msaccess.ex
or the switch will be ignored and you will be using system.mdw

I wouldn't be doing all this over Citrix. Can't you copy the mdb to you
local machine, set up everything and then copy it back

--
Joan Wil
Microsoft Access MV

I'm learning, too, that even once I get to the Secure 97 Database file,

don't have the ability to make a good shortcut, since the drive mapping i
different for the different facility locations. While my executabl
MSACCESS.exe file is on R:, that's not where it is in Tacoma, Washington, o
in Syracuse, NY. And it doesn't appear that I can just have a shortcut tha
points to the database and workgroup without the executable... The databas
opens, but that's just due to filetype association. The workgroup applie
is the one that I have joined, not the one designated in the /wrkgr
argument

Any other ideas would be really appreciated
Thank you Dere
Hi Derek
You have a secure 2000 mdb, right? Therefore you should downloa

dbutilities 1.0 which is for version 2000

Open your 2000 mdb and import all the objects from dbUtilities. G

to th
debug window (Ctrl-G). Typ

DumpPermissions(
The table $tblPermissions will list the permissions - keep thi table
You could then unsecure the 2000 mdb, following the steps in the FAQ
Then convert to 97, and resecure it there using the same group an

use
names that you had in the 2000 version

Then to reapply the permissions, you would ru

LoadPermissions() in the debug windowJoan Wil
Microsoft Access MV