Deployment under Vista
- From: "Sally" <me@xxxxxxxx>
- Date: Sat, 28 Jul 2007 05:36:16 +1000
Firstly, many thanks to those who replied in previous threads in an effort
to guide this idiot along.
Unfortunately the sheer volume of information and some of the (inevitably)
differing opinions made me even more confused. People who have pointed me at
what to them are obvious things understandably get annoyed when I appear not
to have noted them, but in some cases their assertions have been disagreed
with by others. Added to that is my habit of replying on the fly, when there
are more posts to come. Also, I haven't figured out a way of going back
through a thread, so once I've replied to the last post I lose the thread
(literally). I am using CTRL-U to advance through unread messages and my
Outlook (NOT Outlook Express) apparently does not easily allow me step back.
As for VB, I've learned a few things, I hope, and I'll summarise here just
how far I've got and see if there's a way forward that's uncomplicated.
Let's call my app Fred.exe and it uses say two random access files,
Ledger.Dat and Transact.Dat. (not difficult to fathom out what the app
does!).
Anyway, this app works perfectly under XP Home. I have used the PDW Wizard
to deploy it, and the result is
1) The Install suggests that the app is placed in C:\Programs. I accept that
default.
2) As for the data files, I have hardcoded within my app to create a
directory C:\FredsData, and then lines like this
Open "C:\FredsData\Ledger.Dat" For Random As #1 Len=255
As I said, it all works under XP Home.
Now, a colleague is running Vista and I want to post him a CD so that he can
install my app and use it. BUT, I don't want to risk messing up his system,
which runs many critical applications. It is not so serious if he has
trouble running mine. But it would certainly be serious if in attempting to
install mine some files or settings on his Vista were messed up. That was my
anxiety.
So far, I think I have gleaned that
A) Any files apart from my app that PDW bundles on the deployment disc wail
not overwrite any of his that might be later (that cures one worry... IF
I've got that right.
B) The app should not go in root (meaning C: direct). In that respect
perhaps Vista makes a similarly appropriate default suggestion to the
Programs directory in XP Home?
C) The data files should not go in root. In that respect, perhaps my
hardcoded C:\FredsData\... will do the trick?
A, B and C really encapsulate my concerns.
If anyone has the time and patience to reply in as uncomplicated way as
possible, I would be grateful. For those who are fed up with this stupid
bird please do not reply! I guess if no-one replies the message is obvious
and maybe I'll go back to my crochet (sniff)... no knitting here. Perhaps
that challenge will encourage the experts who have difficulty coming down to
a newbie's level not to reply. At times I felt like a 6 year old trying to
understand how subtraction works being given the formula for the resonant
frequency of an LC combination by a learned professor who knows all about
electronics and nothing about 6 year olds.
.
- Follow-Ups:
- Re: Deployment under Vista
- From: Randy Birch
- Re: Deployment under Vista
- From: mayayana
- Re: Deployment under Vista
- From: Pop`
- Re: Deployment under Vista
- From: Rick Raisley
- Re: Deployment under Vista
- From: Ralph
- Re: Deployment under Vista
- Prev by Date: Re: VB6 Debugging non-compiled dll projects
- Next by Date: Re: Show graphics form like in Access
- Previous by thread: VB6 Debugging non-compiled dll projects
- Next by thread: Re: Deployment under Vista
- Index(es):
Relevant Pages
|
Loading
