Advantages of SQL Server

hi ! my boss is thinking of redoing our accounting system which is currently running on FOXPRO - we are planning on a VB/SQL SERVER platform.but he isn't convinced that the benefits of SQL server outweigh those offered by FOXPRO especially since everyone in the office is very comfortable with Foxpro.Can anyone give me some solid advantages of SQL SErver or any other RDBMS over Foxpro ?http://dbforums.com/arch/125/2003/2/689282|||FoxPro?

Accounting?

Security?

I got it...how 'bout an abacus, quill and parchment...

Ok...enough with the sillyness...guess they keep advancing it...why? I have no idea..

http://gotdotnet.com/team/vfp/

What version of foxpro?|||A couple of observations...

VFP and MS-SQL are not mutually exclusive. You can have the benefits of both if you choose. SQL Server can provide the "back end" at the server, and VFP can provide the "front end" at the client.

SQL Server allows much better security, eliminates damaged files due to workstation disconnects, better performance, practically infinite ability to scale.

-PatP|||I still have a Programmer's Manual for FoxPro 2.0, right before it was bought up by M$. It presented a serious competition to Borland's dBase IV, and gave me an opportunity to really dive into SQL...Anybody wants to buy 19 Installation disks (1.44MB) for FoxPro 2.6 with a Connectivity Kit?|||Still got your Access 1.2 disks?

;)

First consultant gig was on 2.0

:D

Now where did all the side business go?

:(|||I've still got a set of 5 1/4 Paradox discs (pre-Windows). 8:)|||Hey, Paradox 4.0/4.5 was my next step (actually a step backwards in regards to SQL) I believe I still have them too, not sure about the version...Anyone?|||...And I also have the first decent VB for DOS, 2.0. Fits on 2 1.44MB floppies, very compact and suitable for travel. Very low minimum system requirements, produces beautiful forms and popup dialog boxes ;)|||Sorry, my old Kaypro doesn't have 3 1/2 inch drives. Just the old 360KB floppies. No HD either.|||I still have a pair of 8" floppies with Vulcan on them.

-PatP|||I knew I should have kept my first program! But carting all those punch cards around got to be a real pain (literally!) :)|||I tossed my paper tape after the program went into production!|||okay..

i used to get up each morning 3 hrs before i went to sleep and clean the road with my tongue, for 3 cents a week. considering the shoebox at the bottom of the lake that we lived in had a rent of 32 cents a week, we had to do a lot of odd jobs.

my first for pay consulting job was at mr slate's quarry.
i used to maintain(feed) the first database ever created called "joe" after it's creator "joe". it used a series of stones tied to sticks attached to a pelican. and through a series of levers we could calculate pi to 1 place in 7.3 hours.
being a very exclusive database, there was only one copy and since it was a bit on the gamey side, it couldnt be kept indoors.

i have a copy in a storage container in my back yard, it's not totally oledb compatible but with a bit of work it could be dblibrary.|||Wow! You still have a copy of the "Joe" database? What a coincidence! At the back of one of my file cabinets I still have the original RFP I submitted for the project.

Did you know it was actually a conversion from an older legacy system?|||nope your thinking of "joe's" weaker sister "mary" it wasnt even a database per se.
the storage mechanism was elephant turds and while being easy to find, were not very portable and therfore would harden after a few days making the db unusable.
we considered mary to be effetively a slowly created statue not a database.

i have a "mary" coffee table if you need some living room furniture.|||Ruprect, the elephant dung can be softened by the application of moisture. This should have been part of your regularly scheduled maintenance plan.

Really, you should have paid more attention to Books On Rocks. It was full of usefull examples. I guess back then you must have been a rookie DBA (Dung Ball Administrator).|||what is it with you
even on older databases your books online is still out of date

[Books On Rocks] Stone Package 3

in the last release of "Mary" database there is no need to apply moisture to the mammoth dung as it is considered a "wasting asset"

you will have to rebuild the dung clusters with fresh dung every one to two weeks for proper retireval.

everyone knows that you will change the "flies" sort order if you moisten the dung

what an ultramaroon..

update your books on rocks|||I stand corrected. I guess my only excuse is that my thinking has been fuzzy and muddled ever since I stumbled upon a strange black rectangular monolith in the woods...

I concede that your knowledge of Dung Ball Administration is much deeper than mine. Knee-deep, even.

ADP Parameterized list box stored proecedure /function

I am trying to populate a list box (MS Access - don't ask it is what my boss wants) with a table-valued function or a stored
procedure. The list box is used to navigate among records that populate the
form, so the same query can be used for the form and the list box thereby,
theoretically, reducing calls to the DB. The records are filtered on two
fields, we'll call them type (GUID) and name (nvarchar), whereby the values
are in two different controls on the form.

The form is using a function, fActiveCompanies, and the imput parameter
propety is completed. The form is able to navigate through the records with
no problem.

I am having difficulty create a SMOOTH method of populating the list box.
currently i am using a stored procedure that is called in VB and populates
the list box with a list of values.

I would prefer to not use a list of values and set the row source type to
Table/View/Stored Procedure.

Please point me in the correct direction for populaitng hte list box not
using a list of values... thank you

Access 2003 - Access Data Projects (ADP) - ADO
SQL Server 2000 (production) SQL Server Express 2005 (devlopment)

my current code for populating the list box is below.

Dim str As String: str = ""
Dim lst As String: lst = ""

Dim rds As ADODB.Recordset
Set rds = New ADODB.Recordset

Forms!frmcompanies!lstCompanies.RowSource = lst
str = "EXEC spActiveCompanies @.pIdTypeCompany='" &
Nz(Forms!frmcompanies!cboTblTypeEntity, "%") & "', @.pNameLegal='" &
Nz(Forms!frmcompanies!txtNav, "%") & "'"

rds.Open str, CurrentProject.Connection

Do Until rds.EOF

If lst = "" Then
lst = """" & rds(0) & """;""" & rds(1) & """"
Else
lst = lst & ";""" & rds(0) & """;""" & rds(1) & """"
End If

rds.MoveNext
Loop

Forms!frmcompanies!lstCompanies.RowSource = lst
Forms!frmcompanies!lstCompanies.Requery

rds.Close: Set rds = Nothing

Forms!frmcompanies.Requery

i mis-read one document, the parameters must be the same as the controls...

field = @.ComboBoxControlName