Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Maintaining connection to SQL Server or not?
Message
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Divers
Thread ID:
01025474
Message ID:
01025499
Vues:
17
Einar,
I am using VFP 9. I have read it too (in some articles in CODE magazine) that this (connect and quickly disconnect) is suggested method.
But I am wondering about how practical it would be in a VFP application. I am concerned that this approach will be too slow (or maybe not), this is why I am asking for someone to share their practical experience.

>Dmitry,
>What language are you using?
>The new way of doing things (according to M$ and ADO.NET) you should connect, get your data into a DataSet (or cursor or whatever) and then disconnect.
>Einar
>
>>I am making baby steps in creating a simple (test) form using n-tier approach. UI -> BO -> DA. That is, UI through BO asks DA for a record and displays it. As user navigates through records in the table, the cycle "UI->BO->DA" will be done quite often (possibly). The DA is where connection to SQL Server takes place.
>>
>>Should I close the connection and open a new one on every call to DA or should I make the connection PUBLIC and maintain it for duration of the form being open?
>>
>>Thank you for any suggestions.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform