desktop SP3 install which is 70MB. Does that make any sense at all as to why
"Mike Epprecht (SQL MVP)" <mike@epprecht.net> wrote in message
news:eXuauiF0EHA.2316@TK2MSFTNGP15.phx.gbl...
> Hi
>
> MSDE2000a is only 43Mb
> (
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=413 > 744d1-a0bc-479f-bafa-e4b278eb9147#filelist)
>
> If you ship the product on CD, include it there, else, you don't have much
> choice but for the customer to download it.
>
> If you use Views or SP's in your project, backporting it to Access will be
> a
> major amount of work, so in effect you will have 2 code bases.
>
> Regards
> --------------------------------
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
>
> IM: mike@epprecht.net
>
> MVP Program:
http://www.microsoft.com/mvp >
> Blog:
http://www.msmvps.com/epprecht/ >
> "TheNortonZ" <thenortonz@hotmail.com> wrote in message
> news:eYkhgkE0EHA.3908@TK2MSFTNGP10.phx.gbl...
>> We have an application (client server, single user, all installed on the
>> users machine) and we use MSDE 2000.
>>
>> One major complaint we have had is that if people download the product
> from
>> the web, it is such a large download (70mb) just for the desktop engine.
>>
>> Our marketing department is now asking what other options we have (to get
>> rid of the large download).
>>
>> I suppose one option would be to change all the SQL stuff to Access but
> then
>> we would have to change the stored procs to queries and I'm not sure what
>> differences there are with this.
>>
>> Any ideas how others have solved this MSDE download issue? What about
> moving
>> everything to Access? Any speculation on how difficult this would be?
>>
>> Oh, BTW, yes, we explained to the marketing folks many many times about
> the
>> size of the download even before we started coding :-)
>>
>> Norton
>>
>>
>
>