yeah I use Setup Factory which hs a template you can download to do the MSDE install. I have already played with that.
The figure of 100 connections was not a LITERAL 100 connections, it was just a figure. In most cases there will only be 10-15 connections. Jeremy -----Original Message----- From: "Leigh Wanstead" <[EMAIL PROTECTED]> To: Multiple recipients of list delphi <[EMAIL PROTECTED]> Date: Thu, 30 Oct 2003 10:49:02 +1300 Subject: RE: [DUG]: Calrification - if anyone can > Hi Jeremy, > > To install MSDE is quite easy, Microsoft got a standard installation in > MSDN > cds. All you need to do is just simply call the setup with some command > line > parameters. I use wise installer to write script to call that setup. > > But MSDE only allow limited concurrent connections, not the figure 100 > you > want. > > Technically speaking if you use my last suggestion, MSDE/MS SQL server > will > only treat your middle tier server application as one single > connection. But > according to MS license, that solution is multiplexing connection. So I > suggestion you to use Ms Access. As Access doesn't have these sorts of > license. > > Regards > Leigh > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of vss > Sent: Thursday, October 30, 2003 10:35 AM > To: Multiple recipients of list delphi > Subject: RE: [DUG]: Calrification - if anyone can > > > Well, my MAIN fear for using MSDE is basically the setup. > I am not the person who will be setting it up, and it might be a non > techincal person doing the installation. > This then introduces a lot of issues that make me , well, > uncomfortable, > if not scared ;-) > My inital thought was MSDE was over kill, as the product will be used > by > Joe blow who uses it on ONE PC to corporates who have a client util on > many machines. > I am TRYING to avoid 2 diff versions, but I guess just thinking about > it, > if I use straight ADO, and not Titan Access 2000, I can just use a > different connection string, although I am not sure what effect this > would have on things like querys. > > How do those of you who use MSDE get on when it comes to installations? > > Jeremy > > -----Original Message----- > From: "Leigh Wanstead" <[EMAIL PROTECTED]> > To: Multiple recipients of list delphi <[EMAIL PROTECTED]> > Date: Thu, 30 Oct 2003 10:19:11 +1300 > Subject: RE: [DUG]: Calrification - if anyone can > > > Hi Jeremy, > > > > My understanding is Access is flat file DB, and is different from SQL > > server. It will face lock problem. > > > > Regards > > Leigh > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > Behalf Of vss > > Sent: Thursday, October 30, 2003 9:30 AM > > To: Multiple recipients of list delphi > > Subject: [DUG]: Calrification - if anyone can > > > > > > For a client utility I have written for another one of my apps. I am > > using ADO to connect to an Access DB. Normally I use Titan Access > 2000 > > controls, but I needed to use ADO because it has the "Sort" property > > where you tell it to sort the data by a field name. > > This is fine, but what I have confused myself about now is, the user > > will > > have the client util running most of the time. > > I am concious of the fact that the ado needs a connection to the > Access > > DB, and this potentually is connected all the time, but since teh > app. > > is > > MDI, when a form is opened, it will then create a connection to the > db, > > and close it when the form is closed. > > BUT if the form is NOT closed, the connection still exists. > > > > What I would like if any on can, is confirmation of the fact that if > > say > > 100 people have a connection to the access db, but its not actually > in > > use, its still ok. Obviously if 100 people are hitting the DB then > > there > > is a problem. > > > > Or to put it another way, a 100 connections is fine, but 100 > > connections > > being used at the same time is a problem. > > > > I hope people understand what I am meaning. > > > > Jeremy > > > > > ----------------------------------------------------------------------- > > ---- > > New Zealand Delphi Users group - Delphi List - > [EMAIL PROTECTED] > > Website: http://www.delphi.org.nz > > To UnSub, send email to: [EMAIL PROTECTED] > > with body of "unsubscribe delphi" > > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ > > > > > > > ----------------------------------------------------------------------- > > ---- > > New Zealand Delphi Users group - Delphi List - > [EMAIL PROTECTED] > > Website: http://www.delphi.org.nz > > To UnSub, send email to: [EMAIL PROTECTED] > > with body of "unsubscribe delphi" > > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ > > ----------------------------------------------------------------------- > ---- > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] > Website: http://www.delphi.org.nz > To UnSub, send email to: [EMAIL PROTECTED] > with body of "unsubscribe delphi" > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ > > > ----------------------------------------------------------------------- > ---- > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] > Website: http://www.delphi.org.nz > To UnSub, send email to: [EMAIL PROTECTED] > with body of "unsubscribe delphi" > Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/ --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi" Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
