|
-
Jul 31st, 2002, 06:43 AM
#1
Thread Starter
Addicted Member
Installing ADO App
Since Im packaging\deploying\installing a VB-SQL-ADO App fr the 1st time, I cant figure out a few things
1.Does the target machine need to have SQL Server Installed on it. ` coz incidentally , the one on which I tried to install does.
2. If it doesnt need to have SQL Installed as I was told by someone, what do I put in the ServerName, UserName and Password entries while opening my ADO Connection ??
-
Jul 31st, 2002, 06:49 AM
#2
-= B u g S l a y e r =-
it would need some kind of db ...
MSDE or SQL server ...
If not you won't be able to use your app...
-
Jul 31st, 2002, 06:51 AM
#3
well
if you made an app that connects to a sql server... then the people you give it to need access to that server.. sql server is an expensive program.. if you made an app you plan to distribute.. then having a sql server as the backend isn't really something you can do. Instead an access database would be more fitting
-
Jul 31st, 2002, 06:53 AM
#4
man imagine buying a program and on the box it says
-system requirements-
Windows 2000, XP
pentium 1Ghz or faster
256 megs ram
300mb HD space
SQL Server 2000
-
Jul 31st, 2002, 06:57 AM
#5
-= B u g S l a y e r =-
Originally posted by kleinma
well
if you made an app that connects to a sql server... then the people you give it to need access to that server.. sql server is an expensive program.. if you made an app you plan to distribute.. then having a sql server as the backend isn't really something you can do. Instead an access database would be more fitting
how about the MSDE its the "light" and free version of SQL Server... that is distributable... I think
-
Jul 31st, 2002, 07:14 AM
#6
Thread Starter
Addicted Member
boo hoo... just when I thought I had something figured out in my life, they tell me to do it all over again....now what is MSDE ?? where can I find comprehensible documentation for it?..and I swear I did hit that Search button on top but It didnt give me anything useful.Can a project using MSSQL7.0 be suddenly, overnight shifted to MSDE ??
-
Jul 31st, 2002, 07:21 AM
#7
if you are using ADO then you could downsize your SQL Server database to an access database without changing any of your code but the actual connection string (ADO is good like that). That way you can distribute the mdb access file with your app...
-
Jul 31st, 2002, 07:32 AM
#8
-= B u g S l a y e r =-
Originally posted by udit99
boo hoo... just when I thought I had something figured out in my life, they tell me to do it all over again....now what is MSDE ?? where can I find comprehensible documentation for it?..and I swear I did hit that Search button on top but It didnt give me anything useful.Can a project using MSSQL7.0 be suddenly, overnight shifted to MSDE ??
take a look at this : http://msdn.microsoft.com/library/de.../msdeforvs.asp
-
Jul 31st, 2002, 07:50 AM
#9
Thread Starter
Addicted Member
and what about the fact that all my recordset populations have been done using Stored Procedures ??
So is the popularity of VB-SQL only because of people designing Customised Software ?? because as a skillset for a prospective job-applicant , VB-Access is kindof frowned upon as inferior.
uhh..kindof funny, but I want to know how a typical Software Development Company would handout the application to its client
a)Burn the setup files on a CD and give it to Client and tell him to Install SQL Server.
b)Buy SQL Server for the client, go to his office, Install SQL Server, then Install your program ????
In case it is option (b) then how do Software development companies cater to Overseas clients.....Air Tickets ??
and Finally.......once the software has been installed at the client's
office and there is this bug in it that is discovered 15 days after operations have commenced, how do you issue a patch that fixes the problem ??
-
Jul 31st, 2002, 08:20 AM
#10
well i work for verizon wireless. I work at one of the customer service call centers... there are 800 people taking calls from customers at any given time.. aspect communications is the vendor we get all the call routing hardware/software from (and trust me it is a lot) this building is just for one area and there is a few million bucks in aspects products here alone... well my point is that the call center is all managed in an oracle database... not only do they provide the database.. but the server it sits on... it is tweaked to perform as they designed it.. and locked down so no one but them can really touch it.
so if you are developing small level apps.. then a database that requires its own server is pretty much not the best course of action...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|