Hi
I have recently upgraded to office 2003 and since doing so, the CurrentUser() function has stopped working in my Access tables - no matter which version - Access 2000, or the converted Access 2003 file, or in new access databases. It does however work in forms!

I have checked the references, and the following are ticked:
Visual Basic for Applications, Microsoft Access 11.0 Object Library, OLE Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO 3.6 Object Library.

Any advice on solving the problem would be appreciated
--
Andre Skeen

No version of Access has ever supported the use of the CurrentUser function
in tables, Andre.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.


"Andre Skeen" <(E-Mail Removed)> wrote in message
news:6FAD916C-B5A2-4608-9882-(E-Mail Removed)...
> Hi
> I have recently upgraded to office 2003 and since doing so, the
CurrentUser() function has stopped working in my Access tables - no matter
which version - Access 2000, or the converted Access 2003 file, or in new
access databases. It does however work in forms!
>
> I have checked the references, and the following are ticked:
> Visual Basic for Applications, Microsoft Access 11.0 Object Library, OLE
Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO 3.6
Object Library.
>
> Any advice on solving the problem would be appreciated
> --
> Andre Skeen

Andre,
Most networks have an enviroment variable defined for usernames, so you could do
Environ$("USERNAME")
as the default value, if thats your situation. Run "Cmd" and type "Set" to see whats available. No real security though. I know currentuser is not available now but I feel I used it in the past at some point.

"Andre Skeen" wrote:

> Hi
> I have recently upgraded to office 2003 and since doing so, the CurrentUser() function has stopped working in my Access tables - no matter which version - Access 2000, or the converted Access 2003 file, or in new access databases. It does however work in forms!
>
> I have checked the references, and the following are ticked:
> Visual Basic for Applications, Microsoft Access 11.0 Object Library, OLE Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO 3.6 Object Library.
>
> Any advice on solving the problem would be appreciated
> --
> Andre Skeen

Environment variables can be reset very easily, so I don't recommend that
they be used in this situation. If you want the network user id, use the API
call, as shown in http://www.mvps.org/access/api/api0008.htm at "The Access
Web".

However, CurrentUser returns the Access user's name, not the network id. In
other words, it assumes Access Security has been applied, so that each user
has to log into the Access application. (If this isn't the case, it'll
return Admin for every user)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)


"peter martin" <peter (E-Mail Removed)> wrote in message
news:1B8CDB53-34D4-46D7-BD18-(E-Mail Removed)...
> Andre,
> Most networks have an enviroment variable defined for usernames, so you
could do
> Environ$("USERNAME")
> as the default value, if thats your situation. Run "Cmd" and type "Set"
to see whats available. No real security though. I know currentuser is not
available now but I feel I used it in the past at some point.
>
> "Andre Skeen" wrote:
>
> > Hi
> > I have recently upgraded to office 2003 and since doing so, the
CurrentUser() function has stopped working in my Access tables - no matter
which version - Access 2000, or the converted Access 2003 file, or in new
access databases. It does however work in forms!
> >
> > I have checked the references, and the following are ticked:
> > Visual Basic for Applications, Microsoft Access 11.0 Object Library, OLE
Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO 3.6
Object Library.
> >
> > Any advice on solving the problem would be appreciated
> > --
> > Andre Skeen

Environ$ is one of the functions that is blocked in the new 'sandbox mode'.
Andre may still be able to use it if he's not using Access 2003, or willing
to turn sandbox mode off, but it's something to consider.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.


"peter martin" <peter (E-Mail Removed)> wrote in message
news:1B8CDB53-34D4-46D7-BD18-(E-Mail Removed)...
> Andre,
> Most networks have an enviroment variable defined for usernames, so you
could do
> Environ$("USERNAME")
> as the default value, if thats your situation. Run "Cmd" and type "Set"
to see whats available. No real security though. I know currentuser is not
available now but I feel I used it in the past at some point.
>
> "Andre Skeen" wrote:
>
> > Hi
> > I have recently upgraded to office 2003 and since doing so, the
CurrentUser() function has stopped working in my Access tables - no matter
which version - Access 2000, or the converted Access 2003 file, or in new
access databases. It does however work in forms!
> >
> > I have checked the references, and the following are ticked:
> > Visual Basic for Applications, Microsoft Access 11.0 Object Library, OLE
Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO 3.6
Object Library.
> >
> > Any advice on solving the problem would be appreciated
> > --
> > Andre Skeen

Thanks for your responses. I am using Access 2003, so I am limited by what it allows.

The short answer then is that CurrentUser is not available for tables, but can be used in forms. The simplest thing for me to do then is to place an invisible field on all my forms, which is easy enough to do. Any other work-around has some limitation or other of it's own. Security is not a major issue for me as yet, but may become so in the future, so I need to take it into account. My database is used by others who may not neccessarily be working from their own machines, so a machine ID/Name wouldn't meet my requirements - a network user might though.

I was using it in Access 2000 tables without a problem, but have found Access 2003 to be much faster over a network and generally superior, so there is no going back.
--
Andre Skeen


"Brendan Reynolds" wrote:

> Environ$ is one of the functions that is blocked in the new 'sandbox mode'.
> Andre may still be able to use it if he's not using Access 2003, or willing
> to turn sandbox mode off, but it's something to consider.
>
> --
> Brendan Reynolds (MVP)
> http://brenreyn.blogspot.com
>
> The spammers and script-kiddies have succeeded in making it impossible for
> me to use a real e-mail address in public newsgroups. E-mail replies to
> this post will be deleted without being read. Any e-mail claiming to be
> from brenreyn at indigo dot ie that is not digitally signed by me with a
> GlobalSign digital certificate is a forgery and should be deleted without
> being read. Follow-up questions should in general be posted to the
> newsgroup, but if you have a good reason to send me e-mail, you'll find
> a useable e-mail address at the URL above.
>
>
> "peter martin" <peter (E-Mail Removed)> wrote in message
> news:1B8CDB53-34D4-46D7-BD18-(E-Mail Removed)...
> > Andre,
> > Most networks have an enviroment variable defined for usernames, so you
> could do
> > Environ$("USERNAME")
> > as the default value, if thats your situation. Run "Cmd" and type "Set"
> to see whats available. No real security though. I know currentuser is not
> available now but I feel I used it in the past at some point.
> >
> > "Andre Skeen" wrote:
> >
> > > Hi
> > > I have recently upgraded to office 2003 and since doing so, the
> CurrentUser() function has stopped working in my Access tables - no matter
> which version - Access 2000, or the converted Access 2003 file, or in new
> access databases. It does however work in forms!
> > >
> > > I have checked the references, and the following are ticked:
> > > Visual Basic for Applications, Microsoft Access 11.0 Object Library, OLE
> Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO 3.6
> Object Library.
> > >
> > > Any advice on solving the problem would be appreciated
> > > --
> > > Andre Skeen
>
>
>

As I am new to this network, I want to first say that I have learned an enormous amount of info from all of you, Thanks very much. . I developed a multiuser database back when we were using Access 2.0. I was able to capture the "user login name" via =Environ$("user") as the default value to a field. Since then, we are now at Windows 2000, and the field DOES NOT recognize this function. I've tried changing it to Environ$("USERNAME") and still no good. . .I've tried the Module of fOSUserName and I can not get that one to work either. . Can someone help. .?

thxs. . . PRTaisho

"Andre Skeen" wrote:

> Thanks for your responses. I am using Access 2003, so I am limited by what it allows.
>
> The short answer then is that CurrentUser is not available for tables, but can be used in forms. The simplest thing for me to do then is to place an invisible field on all my forms, which is easy enough to do. Any other work-around has some limitation or other of it's own. Security is not a major issue for me as yet, but may become so in the future, so I need to take it into account. My database is used by others who may not neccessarily be working from their own machines, so a machine ID/Name wouldn't meet my requirements - a network user might though.
>
> I was using it in Access 2000 tables without a problem, but have found Access 2003 to be much faster over a network and generally superior, so there is no going back.
> --
> Andre Skeen
>
>
> "Brendan Reynolds" wrote:
>
> > Environ$ is one of the functions that is blocked in the new 'sandbox mode'.
> > Andre may still be able to use it if he's not using Access 2003, or willing
> > to turn sandbox mode off, but it's something to consider.
> >
> > --
> > Brendan Reynolds (MVP)
> > http://brenreyn.blogspot.com
> >
> > The spammers and script-kiddies have succeeded in making it impossible for
> > me to use a real e-mail address in public newsgroups. E-mail replies to
> > this post will be deleted without being read. Any e-mail claiming to be
> > from brenreyn at indigo dot ie that is not digitally signed by me with a
> > GlobalSign digital certificate is a forgery and should be deleted without
> > being read. Follow-up questions should in general be posted to the
> > newsgroup, but if you have a good reason to send me e-mail, you'll find
> > a useable e-mail address at the URL above.
> >
> >
> > "peter martin" <peter (E-Mail Removed)> wrote in message
> > news:1B8CDB53-34D4-46D7-BD18-(E-Mail Removed)...
> > > Andre,
> > > Most networks have an enviroment variable defined for usernames, so you
> > could do
> > > Environ$("USERNAME")
> > > as the default value, if thats your situation. Run "Cmd" and type "Set"
> > to see whats available. No real security though. I know currentuser is not
> > available now but I feel I used it in the past at some point.
> > >
> > > "Andre Skeen" wrote:
> > >
> > > > Hi
> > > > I have recently upgraded to office 2003 and since doing so, the
> > CurrentUser() function has stopped working in my Access tables - no matter
> > which version - Access 2000, or the converted Access 2003 file, or in new
> > access databases. It does however work in forms!
> > > >
> > > > I have checked the references, and the following are ticked:
> > > > Visual Basic for Applications, Microsoft Access 11.0 Object Library, OLE
> > Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO 3.6
> > Object Library.
> > > >
> > > > Any advice on solving the problem would be appreciated
> > > > --
> > > > Andre Skeen
> >
> >
> >

What happens when you try to use fOSUserName? I've never heard of that not
working, regardless of the OS and version of Access.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"PRTaisho" <(E-Mail Removed)> wrote in message
news:4D85C454-C4E6-4093-B905-(E-Mail Removed)...
> As I am new to this network, I want to first say that I have learned an
enormous amount of info from all of you, Thanks very much. . I developed a
multiuser database back when we were using Access 2.0. I was able to
capture the "user login name" via =Environ$("user") as the default value to
a field. Since then, we are now at Windows 2000, and the field DOES NOT
recognize this function. I've tried changing it to Environ$("USERNAME") and
still no good. . .I've tried the Module of fOSUserName and I can not get
that one to work either. . Can someone help. .?
>
> thxs. . . PRTaisho
>
> "Andre Skeen" wrote:
>
> > Thanks for your responses. I am using Access 2003, so I am limited by
what it allows.
> >
> > The short answer then is that CurrentUser is not available for tables,
but can be used in forms. The simplest thing for me to do then is to place
an invisible field on all my forms, which is easy enough to do. Any other
work-around has some limitation or other of it's own. Security is not a
major issue for me as yet, but may become so in the future, so I need to
take it into account. My database is used by others who may not neccessarily
be working from their own machines, so a machine ID/Name wouldn't meet my
requirements - a network user might though.
> >
> > I was using it in Access 2000 tables without a problem, but have found
Access 2003 to be much faster over a network and generally superior, so
there is no going back.
> > --
> > Andre Skeen
> >
> >
> > "Brendan Reynolds" wrote:
> >
> > > Environ$ is one of the functions that is blocked in the new 'sandbox
mode'.
> > > Andre may still be able to use it if he's not using Access 2003, or wi
lling
> > > to turn sandbox mode off, but it's something to consider.
> > >
> > > --
> > > Brendan Reynolds (MVP)
> > > http://brenreyn.blogspot.com
> > >
> > > The spammers and script-kiddies have succeeded in making it impossible
for
> > > me to use a real e-mail address in public newsgroups. E-mail replies
to
> > > this post will be deleted without being read. Any e-mail claiming to
be
> > > from brenreyn at indigo dot ie that is not digitally signed by me with
a
> > > GlobalSign digital certificate is a forgery and should be deleted
without
> > > being read. Follow-up questions should in general be posted to the
> > > newsgroup, but if you have a good reason to send me e-mail, you'll
find
> > > a useable e-mail address at the URL above.
> > >
> > >
> > > "peter martin" <peter (E-Mail Removed)> wrote in
message
> > > news:1B8CDB53-34D4-46D7-BD18-(E-Mail Removed)...
> > > > Andre,
> > > > Most networks have an enviroment variable defined for usernames, so
you
> > > could do
> > > > Environ$("USERNAME")
> > > > as the default value, if thats your situation. Run "Cmd" and type
"Set"
> > > to see whats available. No real security though. I know currentuser
is not
> > > available now but I feel I used it in the past at some point.
> > > >
> > > > "Andre Skeen" wrote:
> > > >
> > > > > Hi
> > > > > I have recently upgraded to office 2003 and since doing so, the
> > > CurrentUser() function has stopped working in my Access tables - no
matter
> > > which version - Access 2000, or the converted Access 2003 file, or in
new
> > > access databases. It does however work in forms!
> > > > >
> > > > > I have checked the references, and the following are ticked:
> > > > > Visual Basic for Applications, Microsoft Access 11.0 Object
Library, OLE
> > > Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO
3.6
> > > Object Library.
> > > > >
> > > > > Any advice on solving the problem would be appreciated
> > > > > --
> > > > > Andre Skeen
> > >
> > >
> > >

Actual nothing happens. . Unless I've placed the module at an incorrect property. I've tried at the Default Value and the Control Source of the field. I checked using the CurrentUser() function in the Default Value and it does give me "Admin" as the current user of Access and not the network ID. Sure do appreciate your help. . and thanks again Mr. Steele.. . .

"Douglas J. Steele" wrote:

> What happens when you try to use fOSUserName? I've never heard of that not
> working, regardless of the OS and version of Access.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
> "PRTaisho" <(E-Mail Removed)> wrote in message
> news:4D85C454-C4E6-4093-B905-(E-Mail Removed)...
> > As I am new to this network, I want to first say that I have learned an
> enormous amount of info from all of you, Thanks very much. . I developed a
> multiuser database back when we were using Access 2.0. I was able to
> capture the "user login name" via =Environ$("user") as the default value to
> a field. Since then, we are now at Windows 2000, and the field DOES NOT
> recognize this function. I've tried changing it to Environ$("USERNAME") and
> still no good. . .I've tried the Module of fOSUserName and I can not get
> that one to work either. . Can someone help. .?
> >
> > thxs. . . PRTaisho
> >
> > "Andre Skeen" wrote:
> >
> > > Thanks for your responses. I am using Access 2003, so I am limited by
> what it allows.
> > >
> > > The short answer then is that CurrentUser is not available for tables,
> but can be used in forms. The simplest thing for me to do then is to place
> an invisible field on all my forms, which is easy enough to do. Any other
> work-around has some limitation or other of it's own. Security is not a
> major issue for me as yet, but may become so in the future, so I need to
> take it into account. My database is used by others who may not neccessarily
> be working from their own machines, so a machine ID/Name wouldn't meet my
> requirements - a network user might though.
> > >
> > > I was using it in Access 2000 tables without a problem, but have found
> Access 2003 to be much faster over a network and generally superior, so
> there is no going back.
> > > --
> > > Andre Skeen
> > >
> > >
> > > "Brendan Reynolds" wrote:
> > >
> > > > Environ$ is one of the functions that is blocked in the new 'sandbox
> mode'.
> > > > Andre may still be able to use it if he's not using Access 2003, or wi
> lling
> > > > to turn sandbox mode off, but it's something to consider.
> > > >
> > > > --
> > > > Brendan Reynolds (MVP)
> > > > http://brenreyn.blogspot.com
> > > >
> > > > The spammers and script-kiddies have succeeded in making it impossible
> for
> > > > me to use a real e-mail address in public newsgroups. E-mail replies
> to
> > > > this post will be deleted without being read. Any e-mail claiming to
> be
> > > > from brenreyn at indigo dot ie that is not digitally signed by me with
> a
> > > > GlobalSign digital certificate is a forgery and should be deleted
> without
> > > > being read. Follow-up questions should in general be posted to the
> > > > newsgroup, but if you have a good reason to send me e-mail, you'll
> find
> > > > a useable e-mail address at the URL above.
> > > >
> > > >
> > > > "peter martin" <peter (E-Mail Removed)> wrote in
> message
> > > > news:1B8CDB53-34D4-46D7-BD18-(E-Mail Removed)...
> > > > > Andre,
> > > > > Most networks have an enviroment variable defined for usernames, so
> you
> > > > could do
> > > > > Environ$("USERNAME")
> > > > > as the default value, if thats your situation. Run "Cmd" and type
> "Set"
> > > > to see whats available. No real security though. I know currentuser
> is not
> > > > available now but I feel I used it in the past at some point.
> > > > >
> > > > > "Andre Skeen" wrote:
> > > > >
> > > > > > Hi
> > > > > > I have recently upgraded to office 2003 and since doing so, the
> > > > CurrentUser() function has stopped working in my Access tables - no
> matter
> > > > which version - Access 2000, or the converted Access 2003 file, or in
> new
> > > > access databases. It does however work in forms!
> > > > > >
> > > > > > I have checked the references, and the following are ticked:
> > > > > > Visual Basic for Applications, Microsoft Access 11.0 Object
> Library, OLE
> > > > Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft DAO
> 3.6
> > > > Object Library.
> > > > > >
> > > > > > Any advice on solving the problem would be appreciated
> > > > > > --
> > > > > > Andre Skeen
> > > >
> > > >
> > > >
>
>
>

You can't set the default value to a table field to the results of
fOSUserName (or to any other user-defined function). You must use a form for
input, and set the default property of the text box on the forn to
fOSUserName.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)



"PRTaisho" <(E-Mail Removed)> wrote in message
news:F275FD32-905E-4E2F-B7CE-(E-Mail Removed)...
> Actual nothing happens. . Unless I've placed the module at an incorrect
property. I've tried at the Default Value and the Control Source of the
field. I checked using the CurrentUser() function in the Default Value and
it does give me "Admin" as the current user of Access and not the network
ID. Sure do appreciate your help. . and thanks again Mr. Steele.. . .
>
> "Douglas J. Steele" wrote:
>
> > What happens when you try to use fOSUserName? I've never heard of that
not
> > working, regardless of the OS and version of Access.
> >
> > --
> > Doug Steele, Microsoft Access MVP
> > http://I.Am/DougSteele
> > (no e-mails, please!)
> >
> >
> >
> > "PRTaisho" <(E-Mail Removed)> wrote in message
> > news:4D85C454-C4E6-4093-B905-(E-Mail Removed)...
> > > As I am new to this network, I want to first say that I have learned
an
> > enormous amount of info from all of you, Thanks very much. . I developed
a
> > multiuser database back when we were using Access 2.0. I was able to
> > capture the "user login name" via =Environ$("user") as the default value
to
> > a field. Since then, we are now at Windows 2000, and the field DOES NOT
> > recognize this function. I've tried changing it to Environ$("USERNAME")
and
> > still no good. . .I've tried the Module of fOSUserName and I can not get
> > that one to work either. . Can someone help. .?
> > >
> > > thxs. . . PRTaisho
> > >
> > > "Andre Skeen" wrote:
> > >
> > > > Thanks for your responses. I am using Access 2003, so I am limited
by
> > what it allows.
> > > >
> > > > The short answer then is that CurrentUser is not available for
tables,
> > but can be used in forms. The simplest thing for me to do then is to
place
> > an invisible field on all my forms, which is easy enough to do. Any
other
> > work-around has some limitation or other of it's own. Security is not a
> > major issue for me as yet, but may become so in the future, so I need to
> > take it into account. My database is used by others who may not
neccessarily
> > be working from their own machines, so a machine ID/Name wouldn't meet
my
> > requirements - a network user might though.
> > > >
> > > > I was using it in Access 2000 tables without a problem, but have
found
> > Access 2003 to be much faster over a network and generally superior, so
> > there is no going back.
> > > > --
> > > > Andre Skeen
> > > >
> > > >
> > > > "Brendan Reynolds" wrote:
> > > >
> > > > > Environ$ is one of the functions that is blocked in the new
'sandbox
> > mode'.
> > > > > Andre may still be able to use it if he's not using Access 2003,
or wi
> > lling
> > > > > to turn sandbox mode off, but it's something to consider.
> > > > >
> > > > > --
> > > > > Brendan Reynolds (MVP)
> > > > > http://brenreyn.blogspot.com
> > > > >
> > > > > The spammers and script-kiddies have succeeded in making it
impossible
> > for
> > > > > me to use a real e-mail address in public newsgroups. E-mail
replies
> > to
> > > > > this post will be deleted without being read. Any e-mail claiming
to
> > be
> > > > > from brenreyn at indigo dot ie that is not digitally signed by me
with
> > a
> > > > > GlobalSign digital certificate is a forgery and should be deleted
> > without
> > > > > being read. Follow-up questions should in general be posted to the
> > > > > newsgroup, but if you have a good reason to send me e-mail, you'll
> > find
> > > > > a useable e-mail address at the URL above.
> > > > >
> > > > >
> > > > > "peter martin" <peter (E-Mail Removed)> wrote in
> > message
> > > > > news:1B8CDB53-34D4-46D7-BD18-(E-Mail Removed)...
> > > > > > Andre,
> > > > > > Most networks have an enviroment variable defined for usernames,
so
> > you
> > > > > could do
> > > > > > Environ$("USERNAME")
> > > > > > as the default value, if thats your situation. Run "Cmd" and
type
> > "Set"
> > > > > to see whats available. No real security though. I know
currentuser
> > is not
> > > > > available now but I feel I used it in the past at some point.
> > > > > >
> > > > > > "Andre Skeen" wrote:
> > > > > >
> > > > > > > Hi
> > > > > > > I have recently upgraded to office 2003 and since doing so,
the
> > > > > CurrentUser() function has stopped working in my Access tables -
no
> > matter
> > > > > which version - Access 2000, or the converted Access 2003 file, or
in
> > new
> > > > > access databases. It does however work in forms!
> > > > > > >
> > > > > > > I have checked the references, and the following are ticked:
> > > > > > > Visual Basic for Applications, Microsoft Access 11.0 Object
> > Library, OLE
> > > > > Automation, Microsoft ActiveX Data Objects 2.1 Library, Microsoft
DAO
> > 3.6
> > > > > Object Library.
> > > > > > >
> > > > > > > Any advice on solving the problem would be appreciated
> > > > > > > --
> > > > > > > Andre Skeen
> > > > >
> > > > >
> > > > >
> >
> >
> >