ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> DevelopMentor-dotNET
DevelopMentor-dotNET
Re: [DOTNET] MS Access?
by Darryl Luther other posts by this author
Nov 15 2001 10:01PM messages near this date
Re: [DOTNET] WebService | [DOTNET] ContextMenu.Show() Sample
I'm not getting your argument against MSDE. If something else is using it
and/or depends on it, then it's not sitting around the rest of the time
doing absolutely nothing. In any case, I originally suggested it because the
original poster said something like, "...I don't have SQL 7 yet..." I took
that to mean, "I don't have it yet, but I'll be getting it and will move
this to it then." In this case, it makes a lot more sense to develop against
MSDE and leave Access completely out of the picture. YMMV.

Darryl

>  -----Original Message-----
>  From: Justin Harrell [mailto:justin@[...].COM]
> 
>  I really don't think it would be such a good idea to stop a
>  service that
>  other application may be using and or depend on as is the case with
>  msde. And besides for single user systems a file based db(and I don't
>  mean just jet) can perform better than a server based one
>  like msde. For
>  me MSDE isn't always a good fit and I don't always consider it to be
>  "doing things right", in fact I am getting rather tired of MS's
>  direction and other windows developers in making services and
>  or system
>  tray processes to do something like backup or virus scan, or
>  defrag, or
>  index content, or yes manage db's that might only happen once a day or
>  less yet take up memory and resources the rest of the time while doing
>  absolutely nothing.
> 
>  Justin
> 
>  -----Original Message-----
>  From: Sharpe,Michael [mailto:Michael.Sharpe@[...].COM]
> 
>  In your development, you can tell MSDE to start or stop.  It doesn't
>  have to
>  always be running and taking up resources.  I have an
>  application that I
>  developed in VB6 that uses the SQLDMO to start MSDE, if it isn't
>  already,
>  and stop when the application is finished.  There is no reason any
>  developer
>  should be reliant on Access.  I'm a firm believer in doing it
>  right, not
>  just doing it fast.  Plus scalability to SQL 7.0/2000 is much easier
>  using
>  MSDE than Access.  It might be more development on your end,
>  but it will
>  pay
>  off in the long run.
> 
>  > -----Original Message-----
>  > From: Justin Harrell [SMTP:justin@[...].COM]
>  >
>  > I think a file based db still has plenty of use versus a
>  server based
>  > one like msde. It would be nice to have a direct managed
>  provider for
>  > jet or some other file based db. I really don't want users to have a
>  > service running all the time eating up systems resources
>  when the app
>  > that uses it might only be used once a day or less. At
>  least until sql
>  > server becomes the file system in Blackcomb :).

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved