2007 CurrentUser() How to Login?

[Guest]

I have a question regarding the new access 2007. My old applications used a
workgroup information file to login to a shared database. Many of the
records were filtered by the CurrentUser() expression.

However, I cannot seem to figure out how to prompt for a login name with the
2007 version. I can only see how to password protect the database.

I know that there is help about how to convert previous versions and
maintain user level security but my wishes are to be able to create new
applications with the same ability to filter records based on CurrentUser().

Any insight would be greatly appreciated!

 

[Arvin Meyer [MVP]]

I have a question regarding the new access 2007. My old applications used
a
workgroup information file to login to a shared database. Many of the
records were filtered by the CurrentUser() expression.

However, I cannot seem to figure out how to prompt for a login name with
the
2007 version. I can only see how to password protect the database.

I know that there is help about how to convert previous versions and
maintain user level security but my wishes are to be able to create new
applications with the same ability to filter records based on
CurrentUser().

Any insight would be greatly appreciated!

New databases with the new format cannot use user level security. You can
maintain existing databases which use ULS. If you require ULS, I suggest you
create the database in an earlier version, and maintain it in Access 2007.

 

[David W. Fenton]

You can
maintain existing databases which use ULS. If you require ULS, I
suggest you create the database in an earlier version, and
maintain it in Access 2007.

Uh, can't you create an MDB in A2K7? And apply ULS in A2K7? That is,
why would you need to involve a previous version?

 

[Arvin Meyer [MVP]]

Uh, can't you create an MDB in A2K7? And apply ULS in A2K7? That is,
why would you need to involve a previous version?

If you do everything in code, you can easily enough. I believe that some of
the GUI is missing though.

 

[David W. Fenton]

If you do everything in code, you can easily enough. I believe
that some of the GUI is missing though.

Can you check? It was reported to me that nothing is missing (though
some things may be hard to find).

 

[Arvin Meyer [MVP]]

According to Joan Wild, one of our security experts, the Security Wizard is
missing. Everything else is supposedly there, but hard to find.

 

[Arvin Meyer [MVP]]

Can you check? It was reported to me that nothing is missing (though
some things may be hard to find).

Upon further investigation, everything is still the way it was for MDBs.
There is no ULS at all in the new format.

 

[David W. Fenton]

Upon further investigation, everything is still the way it was for
MDBs.

That is exactly what I thought was the case based on reports I'd
received.

There is no ULS at all in the new format.

Nor any replication.

But the features dropped in the new format are still supported in
MDBs, thankfully.

 

[Guest]

OK, so what is the bottom line here. How do we get a link to the wrkgrp
file. My problem now do I have to make a new workgroup file. I just convert
to 2007 from 2003.

 

[David W. Fenton]

How do we get a link to the wrkgrp
file. My problem now do I have to make a new workgroup file. I
just convert to 2007 from 2003.

Don't convert. Period. Just run the thing in 2007.

 

[Guest]

Dave, I used the wrong word. I did not convert. I just open my 2003 in 2007.
Now Im getting error message, from security wizard you are both log on as the
admin user.
I didn't even log on to anything? It says to fix this problem log on as a
another member of the admins group or import all objects to a new database.

Im doing a test for the 2007 on my hard drive and my workgroup is on a
shared drive. Would that have an issue with it if they are running the 2003?

Or do you think I have to make sure everyone is log off the share drive and
then trying to use the wizard to join the wrkgrp?

Im running out of ideas and Im sure the fix is on my side, but just can't
figure it out.

 

[Joan Wild]

You shouldn't have a problem with others using the mdw at the same time.
Don't join the secure workgroup.

Create a desktop shortcut with the following in the target:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"

"path to msaccess.exe" is the path to the 2007 version of msaccess.exe
"path to mdb" is the path to the secured mdb
"path to mdw" is the path to the secure mdw on the network

 

[Guest]

Problem solved, I had to create a new database and import all objects and
then I had to create a new workgroup file and assign all the users and
permisions. I have the Security.mdw located on hard drive now, but I will
have to copy it to my share drive, which I hope everything goes ok there. It
seems like that Im doing it the hard way.

What do you think Joan?

 

[David W. Fenton]

Problem solved, I had to create a new database and import all
objects and then I had to create a new workgroup file and assign
all the users and permisions.

No, you didn't have to do all of that. You could have followed
Joan's actual instructions and would have saved all that time and
effort.

BTW, in your response to me you said you weren't logged on as admin,
but that's simply not true. Any time you run Access and open a
database and are *not* prompted for a logon, you are transparently
and silently logged on as admin.

 

[Guest]

Dave, you are ever so right. I just kept getting errors. So I said the heck
with and went the other direction. It only took a few more minutes to do it
the hard way. But I would like thank you both for the help. Typical me do
things the hard way.

 

[zyp]

¡¡ÄãºÃ!ÄãµÄÎÄÕÂÎÒÒѶÁ¹ý

Problem solved, I had to create a new database and import all objects and
then I had to create a new workgroup file and assign all the users and
permisions. I have the Security.mdw located on hard drive now, but I will
have to copy it to my share drive, which I hope everything goes ok there.
It
seems like that Im doing it the hard way.

What do you think Joan?