Hi all
I've written a program in VB.NET that allows the user to build quotes for installing shower enclosures. As part of the program, I've included a blank Access database. I've provided them with an interface where they can add their own clients to the database
When the user upgrades to a newer version of my program, I don't want the installer to overwrite the Access database file with my blank one again. How can I tell VB.NET to check to see if the file has been modified, and if so, not to overwrite it
Many thanks
Juggler at(@) sonic dot(.) net
6  3625 
Well, I assume you are upgrading using a setup in vb.net 2003?
If so isn't there a property for the file whatever.mdb to not overwrite?
Of course from within VB.NET you have the system.io.fileinfo class to get
information on files... but that doesn't seem that it would do much good as
far as setup goes.
Check to see if you can't highlight the .MDB file in the setup and click
properties and set to not overwrite. don't have the IDE open at present but
that is where I would look.
HTH,
Shane
"Juggler" <an*******@discussions.microsoft.com> wrote in message
news:FE**********************************@microsof t.com... Hi all,
I've written a program in VB.NET that allows the user to build quotes for
installing shower enclosures. As part of the program, I've included a blank
Access database. I've provided them with an interface where they can add
their own clients to the database.
When the user upgrades to a newer version of my program, I don't want the
installer to overwrite the Access database file with my blank one again. How
can I tell VB.NET to check to see if the file has been modified, and if so,
not to overwrite it?
Many thanks,
Juggler at(@) sonic dot(.) net
I'm using vb.net 2002
When I go to the File System Editor, highlight the file and select properties, I have the option to adjust
- Condition (seems to only check version/processor info on the computer being installed on
- Exclude (blanket exclude from installation
- Folder (where to install it
- Hidden (is it a hidden file
- PackageAs (not sure what this is for
- Permenent (whether or not to leave it during uninstallation
- ReadOnly (read only
- SharedLegacyFile (this might be it, but I don't really know what the help text is talking about
- SourcePath (file location
- System (is it a system file?
- TargetName (name of file
- Transitive (whether or not the installer should reevaluate the Condition property each installation
- Vital (whether a file is vital for installation or not
There must be an answer out there. It's like saving a user's preferences from version to version. Each time I release a new version of the program, I don't want the users to have to re-enter their info. I can work around the installation problem with preferences by using a text file for the user's preferences. When the program loads the splash screen, I check for the existance of the preferences text file. If it's not there, I can display a window to the user that asks for their preferences information (name, whether they want to print in color, etc.), and then write a text file
Thanks for any help that can be provided
Juggler (@)at sonic (.) ne
----- SStory wrote: ----
Well, I assume you are upgrading using a setup in vb.net 2003
If so isn't there a property for the file whatever.mdb to not overwrite
Of course from within VB.NET you have the system.io.fileinfo class to ge
information on files... but that doesn't seem that it would do much good a
far as setup goes
Check to see if you can't highlight the .MDB file in the setup and clic
properties and set to not overwrite. don't have the IDE open at present bu
that is where I would look
HTH
Shan
"Juggler" <an*******@discussions.microsoft.com> wrote in messag
news:FE**********************************@microsof t.com.. Hi all I've written a program in VB.NET that allows the user to build quotes fo
installing shower enclosures. As part of the program, I've included a blan
Access database. I've provided them with an interface where they can ad
their own clients to the database When the user upgrades to a newer version of my program, I don't want th
installer to overwrite the Access database file with my blank one again. Ho
can I tell VB.NET to check to see if the file has been modified, and if so
not to overwrite it Many thanks
Juggler at(@) sonic dot(.) ne
In a similar situation, I did not deliver the default data as part of the
application, but instead built it from the application itself when it did
not exist. That is, the application itself checks for data existing and
builds the default template that way. You could include the default data
as an embedded resource and create it where you want when you want.
"Juggler" <an*******@discussions.microsoft.com> wrote in message
news:4F**********************************@microsof t.com... I'm using vb.net 2002.
When I go to the File System Editor, highlight the file and select
properties, I have the option to adjust:
- Condition (seems to only check version/processor info on the computer
being installed on) - Exclude (blanket exclude from installation)
- Folder (where to install it)
- Hidden (is it a hidden file)
- PackageAs (not sure what this is for)
- Permenent (whether or not to leave it during uninstallation)
- ReadOnly (read only)
- SharedLegacyFile (this might be it, but I don't really know what the
help text is talking about) - SourcePath (file location)
- System (is it a system file?)
- TargetName (name of file)
- Transitive (whether or not the installer should reevaluate the
Condition property each installation) - Vital (whether a file is vital for installation or not)
There must be an answer out there. It's like saving a user's preferences
from version to version. Each time I release a new version of the program,
I don't want the users to have to re-enter their info. I can work around
the installation problem with preferences by using a text file for the
user's preferences. When the program loads the splash screen, I check for
the existance of the preferences text file. If it's not there, I can
display a window to the user that asks for their preferences information
(name, whether they want to print in color, etc.), and then write a text
file.
Thanks for any help that can be provided!
Juggler (@)at sonic (.) net
----- SStory wrote: -----
Well, I assume you are upgrading using a setup in vb.net 2003?
If so isn't there a property for the file whatever.mdb to not
overwrite?
Of course from within VB.NET you have the system.io.fileinfo class
to get information on files... but that doesn't seem that it would do much
good as far as setup goes.
Check to see if you can't highlight the .MDB file in the setup and
click properties and set to not overwrite. don't have the IDE open at
present but that is where I would look.
HTH,
Shane
"Juggler" <an*******@discussions.microsoft.com> wrote in message
news:FE**********************************@microsof t.com... > Hi all, >> I've written a program in VB.NET that allows the user to build
quotes for installing shower enclosures. As part of the program, I've included
a blank Access database. I've provided them with an interface where they can
add their own clients to the database. >> When the user upgrades to a newer version of my program, I don't
want the installer to overwrite the Access database file with my blank one
again. How can I tell VB.NET to check to see if the file has been modified, and
if so, not to overwrite it? >> Many thanks,
>> Juggler at(@) sonic dot(.) net
I like this idea best.
Throw it on the CD... Require them to insert CD first time or whatever and
your program checks to see if it is there using
the fileinfo class and then if not copies it from CD to disk..
Seems the easiest although setup may have a way.. I don't know
Shane
"Ot" <ur***@tds.invalid (use net)> wrote in message
news:%2******************@tk2msftngp13.phx.gbl... In a similar situation, I did not deliver the default data as part of the
application, but instead built it from the application itself when it did
not exist. That is, the application itself checks for data existing and
builds the default template that way. You could include the default data
as an embedded resource and create it where you want when you want.
"Juggler" <an*******@discussions.microsoft.com> wrote in message
news:4F**********************************@microsof t.com... I'm using vb.net 2002.
When I go to the File System Editor, highlight the file and select properties, I have the option to adjust:
- Condition (seems to only check version/processor info on the computer
being installed on) - Exclude (blanket exclude from installation)
- Folder (where to install it)
- Hidden (is it a hidden file)
- PackageAs (not sure what this is for)
- Permenent (whether or not to leave it during uninstallation)
- ReadOnly (read only)
- SharedLegacyFile (this might be it, but I don't really know what the
help text is talking about) - SourcePath (file location)
- System (is it a system file?)
- TargetName (name of file)
- Transitive (whether or not the installer should reevaluate the
Condition property each installation) - Vital (whether a file is vital for installation or not)
There must be an answer out there. It's like saving a user's preferences
from version to version. Each time I release a new version of the program,
I don't want the users to have to re-enter their info. I can work around
the installation problem with preferences by using a text file for the
user's preferences. When the program loads the splash screen, I check for
the existance of the preferences text file. If it's not there, I can
display a window to the user that asks for their preferences information
(name, whether they want to print in color, etc.), and then write a text
file.
Thanks for any help that can be provided!
Juggler (@)at sonic (.) net
----- SStory wrote: -----
Well, I assume you are upgrading using a setup in vb.net 2003?
If so isn't there a property for the file whatever.mdb to not
overwrite?
Of course from within VB.NET you have the system.io.fileinfo class
to get information on files... but that doesn't seem that it would do much
good as far as setup goes.
Check to see if you can't highlight the .MDB file in the setup and
click properties and set to not overwrite. don't have the IDE open at
present but that is where I would look.
HTH,
Shane
"Juggler" <an*******@discussions.microsoft.com> wrote in message
news:FE**********************************@microsof t.com... > Hi all,
>> I've written a program in VB.NET that allows the user to build
quotes for installing shower enclosures. As part of the program, I've included
a blank Access database. I've provided them with an interface where they
can add their own clients to the database. >> When the user upgrades to a newer version of my program, I don't want the installer to overwrite the Access database file with my blank one
again. How can I tell VB.NET to check to see if the file has been modified,
and if so, not to overwrite it? >> Many thanks,
>> Juggler at(@) sonic dot(.) net
I think I'm going to try including the .mdb file with the program, but in a sub-folder. The program will check to see if the .mdb file exists where it should during normal operation, and if it isn't there (i.e. they just installed the program), it will copy the .mdb file from the sub-directory and put it in the proper place before it calls it for the first time
Hopefully, it will all work out. It still seems silly that there isn't a simple setting in vb.net that checks whether or not a file has been modified since the last version update, and to leave it alone if the user has modified it.
Juggle
----- SStory wrote: ----
I like this idea best
Throw it on the CD... Require them to insert CD first time or whatever an
your program checks to see if it is there usin
the fileinfo class and then if not copies it from CD to disk.
Seems the easiest although setup may have a way.. I don't kno
Shan
"Ot" <ur***@tds.invalid (use net)> wrote in messag
news:%2******************@tk2msftngp13.phx.gbl.. In a similar situation, I did not deliver the default data as part of th
application, but instead built it from the application itself when it di
not exist. That is, the application itself checks for data existing an
builds the default template that way. You could include the default dat
as an embedded resource and create it where you want when you want "Juggler" <an*******@discussions.microsoft.com> wrote in messag news:4F**********************************@microsof t.com.. I'm using vb.net 2002 When I go to the File System Editor, highlight the file and selec properties, I have the option to adjust - Condition (seems to only check version/processor info on the compute being installed on - Exclude (blanket exclude from installation
- Folder (where to install it
- Hidden (is it a hidden file
- PackageAs (not sure what this is for
- Permenent (whether or not to leave it during uninstallation
- ReadOnly (read only
- SharedLegacyFile (this might be it, but I don't really know what th
help text is talking about - SourcePath (file location
- System (is it a system file?
- TargetName (name of file
- Transitive (whether or not the installer should reevaluate th
Condition property each installation - Vital (whether a file is vital for installation or not There must be an answer out there. It's like saving a user's preference
from version to version. Each time I release a new version of the program
I don't want the users to have to re-enter their info. I can work aroun
the installation problem with preferences by using a text file for th
user's preferences. When the program loads the splash screen, I check fo
the existance of the preferences text file. If it's not there, I ca
display a window to the user that asks for their preferences informatio
(name, whether they want to print in color, etc.), and then write a tex
file Thanks for any help that can be provided
Juggler (@)at sonic (.) ne
----- SStory wrote: ----
Well, I assume you are upgrading using a setup in vb.net 2003
If so isn't there a property for the file whatever.mdb to no overwrite Of course from within VB.NET you have the system.io.fileinfo clas
to ge information on files... but that doesn't seem that it would do muc
good a far as setup goes Check to see if you can't highlight the .MDB file in the setup an
clic properties and set to not overwrite. don't have the IDE open a
present bu that is where I would look HTH
Shan
"Juggler" <an*******@discussions.microsoft.com> wrote in messag
news:FE**********************************@microsof t.com... Hi all,
I've written a program in VB.NET that allows the user to build
quotes for installing shower enclosures. As part of the program, I've included
a blank Access database. I've provided them with an interface where they
can add their own clients to the database. When the user upgrades to a newer version of my program, I don't want the installer to overwrite the Access database file with my blank one
again. How can I tell VB.NET to check to see if the file has been modified,
and if so, not to overwrite it? Many thanks,
Juggler at(@) sonic dot(.) net
>>>>
There may be... I haven't been using it enough to do formal updates yet.
Simple updates are send them the new exe and they copy over the old one.
Pretty neat, but...
Maybe if there is a way someone at Microsoft or some other guru will respond
and tell us both.
Sorry I don't know more.
Shane
"Juggler" <an*******@discussions.microsoft.com> wrote in message
news:61**********************************@microsof t.com... I think I'm going to try including the .mdb file with the program, but in
a sub-folder. The program will check to see if the .mdb file exists where it
should during normal operation, and if it isn't there (i.e. they just
installed the program), it will copy the .mdb file from the sub-directory
and put it in the proper place before it calls it for the first time.
Hopefully, it will all work out. It still seems silly that there isn't a
simple setting in vb.net that checks whether or not a file has been modified
since the last version update, and to leave it alone if the user has
modified it.
Juggler
----- SStory wrote: -----
I like this idea best.
Throw it on the CD... Require them to insert CD first time or
whatever and your program checks to see if it is there using
the fileinfo class and then if not copies it from CD to disk..
Seems the easiest although setup may have a way.. I don't know
Shane
"Ot" <ur***@tds.invalid (use net)> wrote in message
news:%2******************@tk2msftngp13.phx.gbl... > In a similar situation, I did not deliver the default data as part
of the > application, but instead built it from the application itself when
it did > not exist. That is, the application itself checks for data
existing and > builds the default template that way. You could include the
default data > as an embedded resource and create it where you want when you want. >>> "Juggler" <an*******@discussions.microsoft.com> wrote in message > news:4F**********************************@microsof t.com... >> I'm using vb.net 2002.
>>>> When I go to the File System Editor, highlight the file and
select > properties, I have the option to adjust: >>>> - Condition (seems to only check version/processor info on the
computer > being installed on) >> - Exclude (blanket exclude from installation)
>> - Folder (where to install it)
>> - Hidden (is it a hidden file)
>> - PackageAs (not sure what this is for)
>> - Permenent (whether or not to leave it during uninstallation)
>> - ReadOnly (read only)
>> - SharedLegacyFile (this might be it, but I don't really know what
the > help text is talking about) >> - SourcePath (file location)
>> - System (is it a system file?)
>> - TargetName (name of file)
>> - Transitive (whether or not the installer should reevaluate the
> Condition property each installation) >> - Vital (whether a file is vital for installation or not)
>>>> There must be an answer out there. It's like saving a user's
preferences > from version to version. Each time I release a new version of the
program, > I don't want the users to have to re-enter their info. I can work
around > the installation problem with preferences by using a text file for
the > user's preferences. When the program loads the splash screen, I
check for > the existance of the preferences text file. If it's not there, I
can > display a window to the user that asks for their preferences
information > (name, whether they want to print in color, etc.), and then write a
text > file. >>>> Thanks for any help that can be provided!
>>>> Juggler (@)at sonic (.) net
>>>> ----- SStory wrote: -----
>>>> Well, I assume you are upgrading using a setup in vb.net
2003? >>>> If so isn't there a property for the file whatever.mdb to
not > overwrite? >>>> Of course from within VB.NET you have the
system.io.fileinfo class > to get >> information on files... but that doesn't seem that it would
do much > good as >> far as setup goes.
>>>> Check to see if you can't highlight the .MDB file in the
setup and > click >> properties and set to not overwrite. don't have the IDE open
at > present but >> that is where I would look.
>>>> HTH,
>>>> Shane
>>>> "Juggler" <an*******@discussions.microsoft.com> wrote in
message >> news:FE**********************************@microsof t.com...
>>> Hi all,
>>>> I've written a program in VB.NET that allows the user to build
> quotes for >> installing shower enclosures. As part of the program, I've
included > a blank >> Access database. I've provided them with an interface where
they can > add >> their own clients to the database.
>>>> When the user upgrades to a newer version of my program, I don't > want the >> installer to overwrite the Access database file with my blank
one > again. How >> can I tell VB.NET to check to see if the file has been
modified, and > if so, >> not to overwrite it?
>>>> Many thanks,
>>>> Juggler at(@) sonic dot(.) net
>>>>>>>> This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: david |
last post by:
Hi,
I have some questions about visual studio deployment. I could not find a
way to handle two things, one is how to show a page to let user choose if
they like the executable file run after...
|
by: Mec |
last post by:
Some time ago I created a windows forms application with a deployment
project.
I was always able to build the deployment package after changing the windows
forms application, but somehow something...
|
by: Jo |
last post by:
I am having a real problem with the Launch conditions in VS .NET and can
only come to the conclusion that it is a bug.
It states quite emphatically in the MSDN that Launch Conditions WILL be...
|
by: dawn |
last post by:
Hi,
I've deployed the app I wrote through an Install Wizard project. I place a
link on the user's desktop, and in the program menu, using "shortcut to
primary output....". When I click the icons...
|
by: James |
last post by:
I have a VB windows forms application that accesses a Microsoft Access
database that has been secured using user-level security. The
application is being deployed using No-Touch deployment. The...
|
by: James |
last post by:
I have a VB windows forms application that accesses a Microsoft Access
database that has been secured using user-level security. The
application is being deployed using No-Touch deployment. The...
|
by: Scanner2001 |
last post by:
I have a web service and a deployment project. Inside the deployment
project, is a custom action to create some database related items such as
stored procedures. I have this packaged as an msi, and...
|
by: ComputerGuyCJ |
last post by:
I have an application that I've used click-once deployment to publish out to
a shared network path. From there I installed the app on a few client
machines, including my own. Since then I published...
|
by: andrewbb |
last post by:
I want to deploy a service with a windows app and the setup program
must conform to the Vista certification requirements. Can that be
done with the standard .net setup project? Assuming cost is...
|
by: Sonu |
last post by:
Hi All -
I'm trying to create a setup project using the Setup deployment project
option from Visual Studio 05.
Everything works great except I cannot find how start the application once
user...
|
by: lllomh |
last post by:
Define the method first
this.state = {
buttonBackgroundColor: 'green',
isBlinking: false, // A new status is added to identify whether the button is blinking or not
}
autoStart=()=>{
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 4 Oct 2023 starting at 18:00 UK time (6PM UTC+1) and finishing at about 19:15 (7.15PM)
The start time is equivalent to 19:00 (7PM) in Central...
|
by: Aliciasmith |
last post by:
In an age dominated by smartphones, having a mobile app for your business is no longer an option; it's a necessity. Whether you're a startup or an established enterprise, finding the right mobile app...
|
by: giovanniandrean |
last post by:
The energy model is structured as follows and uses excel sheets to give input data:
1-Utility.py contains all the functions needed to calculate the variables and other minor things (mentions...
|
by: NeoPa |
last post by:
Hello everyone.
I find myself stuck trying to find the VBA way to get Access to create a PDF of the currently-selected (and open) object (Form or Report).
I know it can be done by selecting :...
|
by: isladogs |
last post by:
The next Access Europe meeting will be on Wednesday 1 Nov 2023 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM)
Please note that the UK and Europe revert to winter time on...
|
by: nia12 |
last post by:
Hi there,
I am very new to Access so apologies if any of this is obvious/not clear.
I am creating a data collection tool for health care employees to complete. It consists of a number of...
|
by: NeoPa |
last post by:
Introduction
For this article I'll be focusing on the Report (clsReport) class. This simply handles making the calling Form invisible until all of the Reports opened by it have been closed, when it...
|
by: SueHopson |
last post by:
Hi All,
I'm trying to create a single code (run off a button that calls the Private Sub) for our parts list report that will allow the user to filter by either/both PartVendor and PartType. On...
| |
