Distribute app with MSDE 2000 1

[adrianjohnson]

Hi all,

I downloaded and followed the instructions from this page (

http://msdn2.microsoft.com/en-us/library/aa214935(SQL.80).aspx

) on how to install MSDE 2000. I'm using it in conjunction with a VB6 project.

However, I now need to distribute the project, but all the instuctions I've found mention an unattended installation of MSDE with a file called unattend.iss. All the instructions state I should be able to find this iss file on my machine (I can't), but they seem to point to an earlier version of MSDE and have different installation instructions.

So, how can I distribute my MSDE 2000 database with my VB6 project as a silent (or unattended) install?

Thanks

Adrian

Adrian Johnson
Assystance - i.t. solutions

http://www.assystance.com

 

[dilettante]

Embedding MSDE 2000 Setup into the Setup of Custom Applications may be helpful.

 

[adrianjohnson]

Thanks for the reply. I'll have a play and see what happens.

Adrian Johnson
Assystance - i.t. solutions

http://www.assystance.com

 

[adrianjohnson]

The link provided, and any search I've done, actually didn't help. When it comes to deploying MSDE they all request msdex86.exe - can I find that file. No? Searched in Google/Microsoft - they say it doesn't exist, or I need to download 400Mb of the Windows 2003 SDk to get it. Is it on my VB install CD's? No. How about Office 2000 CD's? Nope. Surely, it must be on this PC, as it has MSDE installed on it? Wrong again. Does this file really exist?

So, all the instructions say, include a file that doesn't exist.

Sorry if this seems like a rant, but it's completely ridiculus. I've spent hours this morning searching for this file with no luck. Yet, everything I've read says I need it.

 

[ChrisHirst]

msdex86.exe is on the Office 2000 Developer disc (\MSDE\) and the setup file is in the same folder but called MSDEInst.iss



Chris.

Indifference will be the downfall of mankind, but who cares?
Woo Hoo! the cobblers kids get new shoes.
People Counting Systems

So long, and thanks for all the fish.

 

[adrianjohnson]

I don't have Office 2000 developer. Is that the only place this file is??

 

[ChrisHirst]

I would think so by now.

MSDE1.0 was updated to the "SQL Server 2000 Desktop Engine" and now MS would like everybody to move on again to the SQL Server 2005 Express Edition.

Given it was a free download at the time I don't suppose it is a problem but I have it in a zip file located at

http://www.candsdesign.co.uk/download/msde.zip

Chris.

Indifference will be the downfall of mankind, but who cares?
Woo Hoo! the cobblers kids get new shoes.
People Counting Systems

So long, and thanks for all the fish.

 

[dilettante]

This article Using SQL Server Desktop Engine Merge Modules makes it all sound a bit dicey anyway. Most of the caveats there apply if you try to use another method of deployment instead of an MSI file built from merge modules too.

I believe they tried to address some of this with SQL Server 2005 Express.

 

[dilettante]

What's in Visual Basic 2005 for the Visual Basic 6.0 Developer looks potentially useful.

 

[adrianjohnson]

I've given Chris' post a star because I needed a certain file and he provided it.

However, I've given ip trying to use it, as I stumble across so many problems! I already had the project in VB6 and was trying to salvage it, but will probably head towards .net - I know how to use and deploy databases with that. It's so much easier. It just means an upgrade of my project.

Thanks for the help people.

Adrian Johnson

http://www.amanian.co.uk

http://www.adrian-johnson.com

 

[SBerthold]

I would use a user interface which shows the installation of my application, and/or the installation of SQL Server Express, or MSDE, among other things. The UI checks if already installed and what version and greys out the selection if not needed to be installed, or doesn't allow the application to be installed until the user installed the other component(s).

It is still a two-step installation, but all from the same starting point, and the user is aware of what is going on (3rd party license agreements, etc.).