I'm sorry you have run into this problem.
We also have the new Dells. We have encountered this problem on a new Dell w/ windows 2000/Access 2000 and XP/Access 2000.
I have a Dell laptop loaded with XP/Access 2000.
If I login as Administrator and access my .MDB on the C:\ drive, I no longer get the problem.
If I login as Administrator and access my .MDB on a network drive, I no longer get the problem.
If I login as myself (and I have admin privs) and access my .MDB on the C:\ drive or a network drive I get a permissions problem, stating that Access cannot access my file due to Internet permissions. As I do not have the laptop presently in front of me I cannot give you the exact error message, but you get the idea.
Our Network Administor thinks there may be specific permissions for MS Access which need to be changed.
But I still have the question you do:
!!! So shouldn't we just be looking at VB
/ VBA references - whatever they are? !!!
I've search the internet like you and have no solution yet.
I think it's about time to call Microsoft Support and see if they have a solution for this problem.
I'll keep you posted as to what or if we find anything. Please let me know if you find a solution.
Originally posted by timmer
I also ran into this problem with ENVIRON / RTRIM / FORMAT.
An odd one I noticed is that the command PRINT ENVIRON("USERNAME") works in a VBA immediate window but will not work in a text object on a form or report.
I posted this problem to Microsoft's Access FormDesign newsgroup and got a nice reply including code to call an API for the user name. I also got replies from others who have encountered this same problem.
WHY DOES ENVRON WORK ON SOME MACHINES & NOT OTHERS!!!
I just encounter this problem with the latest computers we got from DELL. The only way I got the forms to display the Username using ENVIRON on these new Dell machines was to reload the operating system. We order these machines from Dell with OfficeXP Small Business. I do not want to have to rebuild every new machine we buy.
I checked the references, dates & version. They match on the older functioning machines with the newer nonfunctioning Dell.
Also, the above functions are VB
functions. So shouldn't we just be looking at VB
/ VBA references - whatever they are?
Thanks for any help you might offer. [/SIZE][/QUOTE]