|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Update Workstations with new executableI have written a bunch of Visual Basic 6 programs for which we run Inventory, Order Entry etc. There are numerous .exe's and some are updated on regular basis. We have a folder on a network call "Programs" where are the executables (.exe) are stored and the workstations have shortcuts mapped to the drive and to the specific program they need to run. This is not a big problem but would be time saver if there was a way to do the following: Every time I recompile a program I copy the .exe over to Program folder from the development system. Each time I have to get everyone out of the program to complete the copy. Is there a routine either I can borrow or buy that would alert a user that there is a new version of their executable the next time they open up the program. Hopefully it would alert them of the update and do the update. Thanks, Bob Leffew Bob...
I had the same situation. I created a startup app that runs in the same folder as the main app. See attached VB6 forms. The Form_Load checks the version number of the the main exe and compares to the version of the exe in the network folder. If the versions are different the network version is copied. Shell starts the main exe. You just need to get the startup app on each workstation and point them to it instead of the main exe. Show quoteHide quote "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message [attached file: frmStartUp.frx]news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > We have a small shop of 15 users. > > I have written a bunch of Visual Basic 6 programs for which we run > Inventory, Order Entry etc. > > There are numerous .exe's and some are updated on regular basis. > > We have a folder on a network call "Programs" where are the executables > (.exe) are stored and the workstations have shortcuts mapped to the drive > and to the specific program they need to run. > > This is not a big problem but would be time saver if there was a way to do > the following: > > Every time I recompile a program I copy the .exe over to Program folder from > the development system. Each time I have to get everyone out of the program > to complete the copy. > > Is there a routine either I can borrow or buy that would alert a user that > there is a new version of their executable the next time they open up the > program. Hopefully it would alert them of the update and do the update. > > Thanks, > > Bob Leffew > > [attached file: frmStartUp.frm] Thanks,
I couldnt download the attachements told me Unsafe. Could you put them in a zip file? Thanks again, Bob Show quoteHide quote "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message news:%23jd28RqzFHA.2652@TK2MSFTNGP14.phx.gbl... > Bob... > I had the same situation. I created a startup app that runs in the same > folder as the main app. See attached VB6 forms. > The Form_Load checks the version number of the the main exe and compares to > the version of the exe in the network folder. If the versions are different > the network version is copied. Shell starts the main exe. > You just need to get the startup app on each workstation and point them to > it instead of the main exe. > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > > We have a small shop of 15 users. > > > > I have written a bunch of Visual Basic 6 programs for which we run > > Inventory, Order Entry etc. > > > > There are numerous .exe's and some are updated on regular basis. > > > > We have a folder on a network call "Programs" where are the executables > > (.exe) are stored and the workstations have shortcuts mapped to the drive > > and to the specific program they need to run. > > > > This is not a big problem but would be time saver if there was a way to do > > the following: > > > > Every time I recompile a program I copy the .exe over to Program folder > from > > the development system. Each time I have to get everyone out of the > program > > to complete the copy. > > > > Is there a routine either I can borrow or buy that would alert a user that > > there is a new version of their executable the next time they open up the > > program. Hopefully it would alert them of the update and do the update. > > > > Thanks, > > > > Bob Leffew > > > > > > > I do have one question.
They may have multiple .exe shortcutted to their desktop. Again all coming from a network drive. Does it work for this type environment? Thanks, Bob Leffew Show quoteHide quote "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message news:%23jd28RqzFHA.2652@TK2MSFTNGP14.phx.gbl... > Bob... > I had the same situation. I created a startup app that runs in the same > folder as the main app. See attached VB6 forms. > The Form_Load checks the version number of the the main exe and compares to > the version of the exe in the network folder. If the versions are different > the network version is copied. Shell starts the main exe. > You just need to get the startup app on each workstation and point them to > it instead of the main exe. > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > > We have a small shop of 15 users. > > > > I have written a bunch of Visual Basic 6 programs for which we run > > Inventory, Order Entry etc. > > > > There are numerous .exe's and some are updated on regular basis. > > > > We have a folder on a network call "Programs" where are the executables > > (.exe) are stored and the workstations have shortcuts mapped to the drive > > and to the specific program they need to run. > > > > This is not a big problem but would be time saver if there was a way to do > > the following: > > > > Every time I recompile a program I copy the .exe over to Program folder > from > > the development system. Each time I have to get everyone out of the > program > > to complete the copy. > > > > Is there a routine either I can borrow or buy that would alert a user that > > there is a new version of their executable the next time they open up the > > program. Hopefully it would alert them of the update and do the update. > > > > Thanks, > > > > Bob Leffew > > > > > > > My solution to that was to create a startup exe for each application. You
could hard code it all into one startup app I suppose...I zipped the whole startup app... Show quoteHide quote "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message [attached file: Startup.zip]news:uvXz4WqzFHA.3772@TK2MSFTNGP12.phx.gbl... > I do have one question. > > They may have multiple .exe shortcutted to their desktop. Again all coming > from a network drive. > > Does it work for this type environment? > > Thanks, > > Bob Leffew > > > "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message > news:%23jd28RqzFHA.2652@TK2MSFTNGP14.phx.gbl... > > Bob... > > I had the same situation. I created a startup app that runs in the same > > folder as the main app. See attached VB6 forms. > > The Form_Load checks the version number of the the main exe and compares > to > > the version of the exe in the network folder. If the versions are > different > > the network version is copied. Shell starts the main exe. > > You just need to get the startup app on each workstation and point them to > > it instead of the main exe. > > > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > > news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > > > We have a small shop of 15 users. > > > > > > I have written a bunch of Visual Basic 6 programs for which we run > > > Inventory, Order Entry etc. > > > > > > There are numerous .exe's and some are updated on regular basis. > > > > > > We have a folder on a network call "Programs" where are the executables > > > (.exe) are stored and the workstations have shortcuts mapped to the > drive > > > and to the specific program they need to run. > > > > > > This is not a big problem but would be time saver if there was a way to > do > > > the following: > > > > > > Every time I recompile a program I copy the .exe over to Program folder > > from > > > the development system. Each time I have to get everyone out of the > > program > > > to complete the copy. > > > > > > Is there a routine either I can borrow or buy that would alert a user > that > > > there is a new version of their executable the next time they open up > the > > > program. Hopefully it would alert them of the update and do the update. > > > > > > Thanks, > > > > > > Bob Leffew > > > > > > > > > > > > > > Looks great, thanks.
Looking it over I have these questions: How does it know where the user has the .exe stored on their local system? strCurrentVersion = GetFileVersion(App.Path & "\inventory.exe") Does this automatically find the file on their system? I assume I change the following to match my network drive. strLatestVersion = GetFileVersion("m:\inv\live\inventory.exe") Does the Grid thing apply to me? Thanks, Bob Show quoteHide quote "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message news:eKuFhdqzFHA.2076@TK2MSFTNGP14.phx.gbl... > My solution to that was to create a startup exe for each application. You > could hard code it all into one startup app I suppose...I zipped the whole > startup app... > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > news:uvXz4WqzFHA.3772@TK2MSFTNGP12.phx.gbl... > > I do have one question. > > > > They may have multiple .exe shortcutted to their desktop. Again all > coming > > from a network drive. > > > > Does it work for this type environment? > > > > Thanks, > > > > Bob Leffew > > > > > > "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message > > news:%23jd28RqzFHA.2652@TK2MSFTNGP14.phx.gbl... > > > Bob... > > > I had the same situation. I created a startup app that runs in the same > > > folder as the main app. See attached VB6 forms. > > > The Form_Load checks the version number of the the main exe and compares > > to > > > the version of the exe in the network folder. If the versions are > > different > > > the network version is copied. Shell starts the main exe. > > > You just need to get the startup app on each workstation and point them > to > > > it instead of the main exe. > > > > > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > > > news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > > > > We have a small shop of 15 users. > > > > > > > > I have written a bunch of Visual Basic 6 programs for which we run > > > > Inventory, Order Entry etc. > > > > > > > > There are numerous .exe's and some are updated on regular basis. > > > > > > > > We have a folder on a network call "Programs" where are the > executables > > > > (.exe) are stored and the workstations have shortcuts mapped to the > > drive > > > > and to the specific program they need to run. > > > > > > > > This is not a big problem but would be time saver if there was a way > to > > do > > > > the following: > > > > > > > > Every time I recompile a program I copy the .exe over to Program > folder > > > from > > > > the development system. Each time I have to get everyone out of the > > > program > > > > to complete the copy. > > > > > > > > Is there a routine either I can borrow or buy that would alert a user > > that > > > > there is a new version of their executable the next time they open up > > the > > > > program. Hopefully it would alert them of the update and do the > update. > > > > > > > > Thanks, > > > > > > > > Bob Leffew > > > > > > > > > > > > > > > > > > > > > > > > The startup exe and the main exe reside in the same local folder. What I
did was changed the users workstation shortcuts to point to the startup exe instead of the main exe. (don't forget to change the shortcut from the Programs menu, if you have one, as well as desktop shortcuts) The code uses App.Path to determine the local path to copy to. Substitute my "m:\inv\live\inventory.exe" for your network path and file name(s) Disregard the grid and dll copies and the regserver call. Show quoteHide quote "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message news:%230kE7kqzFHA.1168@TK2MSFTNGP15.phx.gbl... > Looks great, thanks. > > Looking it over I have these questions: > > How does it know where the user has the .exe stored on their local > system? > > strCurrentVersion = GetFileVersion(App.Path & "\inventory.exe") > Does this automatically find the file on their system? > > I assume I change the following to match my network drive. > > strLatestVersion = GetFileVersion("m:\inv\live\inventory.exe") > > Does the Grid thing apply to me? > > Thanks, > > Bob > > > "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message > news:eKuFhdqzFHA.2076@TK2MSFTNGP14.phx.gbl... > > My solution to that was to create a startup exe for each application. You > > could hard code it all into one startup app I suppose...I zipped the whole > > startup app... > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > > news:uvXz4WqzFHA.3772@TK2MSFTNGP12.phx.gbl... > > > I do have one question. > > > > > > They may have multiple .exe shortcutted to their desktop. Again all > > coming > > > from a network drive. > > > > > > Does it work for this type environment? > > > > > > Thanks, > > > > > > Bob Leffew > > > > > > > > > "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message > > > news:%23jd28RqzFHA.2652@TK2MSFTNGP14.phx.gbl... > > > > Bob... > > > > I had the same situation. I created a startup app that runs in the > same > > > > folder as the main app. See attached VB6 forms. > > > > The Form_Load checks the version number of the the main exe and > compares > > > to > > > > the version of the exe in the network folder. If the versions are > > > different > > > > the network version is copied. Shell starts the main exe. > > > > You just need to get the startup app on each workstation and point > them > > to > > > > it instead of the main exe. > > > > > > > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > > > > news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > > > > > We have a small shop of 15 users. > > > > > > > > > > I have written a bunch of Visual Basic 6 programs for which we run > > > > > Inventory, Order Entry etc. > > > > > > > > > > There are numerous .exe's and some are updated on regular basis. > > > > > > > > > > We have a folder on a network call "Programs" where are the > > executables > > > > > (.exe) are stored and the workstations have shortcuts mapped to the > > > drive > > > > > and to the specific program they need to run. > > > > > > > > > > This is not a big problem but would be time saver if there was a way > > to > > > do > > > > > the following: > > > > > > > > > > Every time I recompile a program I copy the .exe over to Program > > folder > > > > from > > > > > the development system. Each time I have to get everyone out of the > > > > program > > > > > to complete the copy. > > > > > > > > > > Is there a routine either I can borrow or buy that would alert a > user > > > that > > > > > there is a new version of their executable the next time they open > up > > > the > > > > > program. Hopefully it would alert them of the update and do the > > update. > > > > > > > > > > Thanks, > > > > > > > > > > Bob Leffew > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I forgot one thing - if you use this idea - just make sure you have your VB
project's version number set to auto increment (on the Project properties dialog - Make tab), so that each time you rebuild you'll get a new version number for the exe. This is also handy for when you put out a bad exe - if you delete the bad exe from the network folder and replace it with the older working version - the older working version will get copied back to the workstations... Tom Show quoteHide quote "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message news:uvXz4WqzFHA.3772@TK2MSFTNGP12.phx.gbl... > I do have one question. > > They may have multiple .exe shortcutted to their desktop. Again all coming > from a network drive. > > Does it work for this type environment? > > Thanks, > > Bob Leffew > > > "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message > news:%23jd28RqzFHA.2652@TK2MSFTNGP14.phx.gbl... > > Bob... > > I had the same situation. I created a startup app that runs in the same > > folder as the main app. See attached VB6 forms. > > The Form_Load checks the version number of the the main exe and compares > to > > the version of the exe in the network folder. If the versions are > different > > the network version is copied. Shell starts the main exe. > > You just need to get the startup app on each workstation and point them to > > it instead of the main exe. > > > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > > news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > > > We have a small shop of 15 users. > > > > > > I have written a bunch of Visual Basic 6 programs for which we run > > > Inventory, Order Entry etc. > > > > > > There are numerous .exe's and some are updated on regular basis. > > > > > > We have a folder on a network call "Programs" where are the executables > > > (.exe) are stored and the workstations have shortcuts mapped to the > drive > > > and to the specific program they need to run. > > > > > > This is not a big problem but would be time saver if there was a way to > do > > > the following: > > > > > > Every time I recompile a program I copy the .exe over to Program folder > > from > > > the development system. Each time I have to get everyone out of the > > program > > > to complete the copy. > > > > > > Is there a routine either I can borrow or buy that would alert a user > that > > > there is a new version of their executable the next time they open up > the > > > program. Hopefully it would alert them of the update and do the update. > > > > > > Thanks, > > > > > > Bob Leffew > > > > > > > > > > > > > > Worked like a charm.
I really do appreciate it. Thanks a bunch. Bob Leffew Show quoteHide quote "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message news:%239M7OhqzFHA.1252@TK2MSFTNGP09.phx.gbl... > I forgot one thing - if you use this idea - just make sure you have your VB > project's version number set to auto increment (on the Project properties > dialog - Make tab), so that each time you rebuild you'll get a new version > number for the exe. This is also handy for when you put out a bad exe - if > you delete the bad exe from the network folder and replace it with the older > working version - the older working version will get copied back to the > workstations... > > Tom > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > news:uvXz4WqzFHA.3772@TK2MSFTNGP12.phx.gbl... > > I do have one question. > > > > They may have multiple .exe shortcutted to their desktop. Again all > coming > > from a network drive. > > > > Does it work for this type environment? > > > > Thanks, > > > > Bob Leffew > > > > > > "Tom Gaughan" <tgaughan@no2spam.numail.org> wrote in message > > news:%23jd28RqzFHA.2652@TK2MSFTNGP14.phx.gbl... > > > Bob... > > > I had the same situation. I created a startup app that runs in the same > > > folder as the main app. See attached VB6 forms. > > > The Form_Load checks the version number of the the main exe and compares > > to > > > the version of the exe in the network folder. If the versions are > > different > > > the network version is copied. Shell starts the main exe. > > > You just need to get the startup app on each workstation and point them > to > > > it instead of the main exe. > > > > > > "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message > > > news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > > > > We have a small shop of 15 users. > > > > > > > > I have written a bunch of Visual Basic 6 programs for which we run > > > > Inventory, Order Entry etc. > > > > > > > > There are numerous .exe's and some are updated on regular basis. > > > > > > > > We have a folder on a network call "Programs" where are the > executables > > > > (.exe) are stored and the workstations have shortcuts mapped to the > > drive > > > > and to the specific program they need to run. > > > > > > > > This is not a big problem but would be time saver if there was a way > to > > do > > > > the following: > > > > > > > > Every time I recompile a program I copy the .exe over to Program > folder > > > from > > > > the development system. Each time I have to get everyone out of the > > > program > > > > to complete the copy. > > > > > > > > Is there a routine either I can borrow or buy that would alert a user > > that > > > > there is a new version of their executable the next time they open up > > the > > > > program. Hopefully it would alert them of the update and do the > update. > > > > > > > > Thanks, > > > > > > > > Bob Leffew > > > > > > > > > > > > > > > > > > > > > > > Ok this is a hack and others might have a more guruish solution. Create an
INI file in the shared folder... Each time you compile your app you update the app version in the INI file. Each time the other apps log in to the folder they would compare their version (App.Major & " " & App.Minor) to the version indicated in the INI. If older then prompt user to change their exe. A hack but should do the job. Show quoteHide quote "Bob Leffew" <rlef***@harwood-intl.com.nospam> wrote in message news:%23%23LtUGqzFHA.612@TK2MSFTNGP10.phx.gbl... > We have a small shop of 15 users. > > I have written a bunch of Visual Basic 6 programs for which we run > Inventory, Order Entry etc. > > There are numerous .exe's and some are updated on regular basis. > > We have a folder on a network call "Programs" where are the executables > (.exe) are stored and the workstations have shortcuts mapped to the drive > and to the specific program they need to run. > > This is not a big problem but would be time saver if there was a way to do > the following: > > Every time I recompile a program I copy the .exe over to Program folder from > the development system. Each time I have to get everyone out of the program > to complete the copy. > > Is there a routine either I can borrow or buy that would alert a user that > there is a new version of their executable the next time they open up the > program. Hopefully it would alert them of the update and do the update. > > Thanks, > > Bob Leffew > > 
Other interesting topics
Command Button Sequence
Avoid Overflow! 3 dimenional control array populating combobox form_load parameters - novice Need to know when a process is exited Best way to have a subroutine modify more than one variable Scheduling Control Expot datas in to excel sheet debugging vb6 activex dll under apache/tomcat |
|||||||||||||||||||||||
