Re: Development considerations for Win XP
- From: "Jim Carlock" <anonymous@localhost>
- Date: Sun, 17 Jul 2005 21:49:57 -0400
For the most part, XP won't allow regular users to access
information stored in other users areas of the hard disk.
Windows 2000 works in the same manner, and I believe
WinNT 4.0 as well. Any OS may bear different areas of
the hard disk that might not be updateable, like the Windows
or WinNT folder, the Program Files\Common Files area,
etc.
You should be okay, unless you're trying to do something
that a firewall might trap, or that you don't have permissions
to do. In those cases you might need to ask the end user
to install while logged in as an Administrator.
Hope this helps.
--
Jim Carlock
Please post replies to newsgroup.
"VanS" <VanS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello,
I have a VB6 frontend to an Excel/Word VBA app which I will market to
clients with a variety of platforms but I hope to support only back to Win ME
or 2K and Office 2000 and forward to Win XP and latest Office. The product is
already developed. But I am learning that I need to assemble and test my app
under a user account rather than the Admin under Win XP to be sure it will
work.
I am not up to speed that much on XP but can anyone tell me what
considerations I need to take into account in developing under XP, whether
under network or standalone, and other considerations. I am starting to
research under MS KB and MSDN but if you know of any resources would also be
appreciate.
Thanks for any help, God bless
Van
.
- Follow-Ups:
- Re: Development considerations for Win XP
- From: VanS
- Re: Development considerations for Win XP
- References:
- Development considerations for Win XP
- From: VanS
- Development considerations for Win XP
- Prev by Date: Re: FSO read file not working
- Next by Date: Re: How to change menu font size at runtime?
- Previous by thread: Development considerations for Win XP
- Next by thread: Re: Development considerations for Win XP
- Index(es):
Relevant Pages
|
Loading