If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Data Access, Manipulation & Batch Languages > Delphi, C etc > Package & Deployment Wizard

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 02-21-04, 04:21
SunitaGoswami SunitaGoswami is offline
Registered User
 
Join Date: Oct 2003
Posts: 5
Package & Deployment Wizard

Hello,

Did anybody ever change the source code of the setup1.vbp in the Package & Deployment Wizard. If yes please reply ASAP.
I want to do its error handling. & run osql through the code.

Thanks in advance.
Reply With Quote
  #2 (permalink)  
Old 02-22-04, 16:54
brianb99999 brianb99999 is offline
Registered User
 
Join Date: Feb 2004
Posts: 37
Hi,

I have modified the setup1 from PDW before, it is normally stored in:
C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Setup1
open setup1.vbp in this directory and program as a normal vb app.

Brian.
Reply With Quote
  #3 (permalink)  
Old 02-22-04, 23:18
SunitaGoswami SunitaGoswami is offline
Registered User
 
Join Date: Oct 2003
Posts: 5
Help

Quote:
Originally posted by brianb99999
Hi,

I have modified the setup1 from PDW before, it is normally stored in:
C:\Program Files\Microsoft Visual Studio\VB98\Wizards\PDWizard\Setup1
open setup1.vbp in this directory and program as a normal vb app.

Brian.
Hi Brian ,
I have already changed quite a bit of the setup1.vbp. I am able to run sql scripts in the setup1.vbp through osql command. But if ms sql server is uninstall the setup1.vbp is unable to detect that & still moves further with tha setup.
Can you throw some light on that.
Sunita
Reply With Quote
  #4 (permalink)  
Old 02-23-04, 00:31
brianb99999 brianb99999 is offline
Registered User
 
Join Date: Feb 2004
Posts: 37
Hi Sunita,

Ahhh, I see. I thought...
If vb is not throwing any type of error event, then the best way might be to find a reliable reference in the registry which sql always uses only when installed (maybe a version number, path or licence key), if the reference exists, then you have a pretty good idea that ms sql is on the machine (might work, but not perfect, cause if MS SQL was installed and later incorrectly removed, then the reg item you pick may still exist even though MS SQL has been removed).
Also, make sure that VB's error handling hasn't been turned off (can't remember how this is done, just remember that there is a way and the writers of Setup1 may have done it).

Regs,
Brian.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On