Re: Development considerations for Win XP

Jim,
Thanks for your reply. From my limited reading thus far, it appears this
could be a major issue to deal with potentially. Microsoft advises developers
to develop for the LUAs-the limited user accounts rather than under
Administrator if apps are to work. Even major software vendors have failed to
heed this caveat and their apps have bombed. This will be even more critical
under Longhorn.
I'm still researching but for practicality will tell my users to install
under Administrator mode until I can get the LUA version out.
Thanks again, God bless
Van
"Jim Carlock" wrote:

> 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
>
>
>
.

Relevant Pages

  • Re: Over 100 Microsoft MVPs Have Signed Online Petition - Give Us Back VB!!
    ... Most serious VB apps, by necessity, use a fair ... > understand that Delphi 3rd party components have also all but dried up. ... I assume VB developers could do the same? ... because of the language per se, it's because if I go there I know I'll have ...
    (borland.public.delphi.non-technical)
  • Re: Is that a joke ?
    ... than C++ apps for most uses. ... It probably looks fast to Java or VB developers but what ... > What about CAD, CAE, CAM, scientific applications, utilities, math, ... a garbage collector doesn't make good programmers or safe ...
    (microsoft.public.dotnet.general)
  • Re: Camera Card Reader
    ... I am NOT in the business of beta testing with my Visa ... millions of it's existing customers by obsoleting their legacy apps ... developers can afford! ... private and public betas and from first vision to final production ...
    (rec.photo.digital)
  • Re: Replacement of PDA and phone
    ... open source, have thousands of apps available, which give them a head-start ... come up with a functional analog and once I migrate my data I ... Sure, but it presupposes that 3rd-party developers embrace the platform, ...
    (alt.cellular.cingular)
  • Re: Is that a joke ?
    ... To Jim and Ted: ... You're just another bunch of Anti-Microsoft fools. ... >> Managed code might be fast enough for enterprise apps, ... It probably looks fast to Java or VB developers but what ...
    (microsoft.public.dotnet.general)