Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Remote Processing Best Practice
Message
De
31/01/2005 15:04:14
James Blackburn
Qualty Design Systems, Inc.
Kuna, Idaho, États-Unis
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Client/serveur
Versions des environnements
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP1
Network:
Windows 2000 Server
Database:
MS SQL Server
Divers
Thread ID:
00982271
Message ID:
00982414
Vues:
37
I would do all the processing with a sp. I have found very little that VFP can do that the server I work with (ASA) can't and I can't believe that SQL server is less capable. It is mainly a mindset issue having worked mainly in VFP. It took me a long time to start thinking in datasets instead of rows. By using temp tables and cursors you can accomplish a lot.

>>Chad,
>>
>>I don't use MSSQl Server but I am sure you can do this with a Stored Procedure. That would be the most efficient. JMHO.
>
>Do what exactly with a stored proc? Launch the process? Check on the process? Do the whole process? I know I can use stored procs in a variety of places, but performance of SQL Server in iterative processes...well...sucks! VFP kills SQL when it comes to iterating through sets of data. If I could do the whole process updating sets, then, yes, SQL Server stored proc would be the place to do it, but I *HAVE* to do multiple embedded scans and loops for the processing to work properly.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform