Why is necessary to use and intermediate thread sometimes(like FoxPro or VB) when using SQL Server?
Huh? FoxPro is another database type while VB is Visual Basic, the programming language. The only reason I would know of to use FoxPro is when transferring data between the two DBs, and I'm just guessing there. I've never actually heard of anyone using FoxPro with SQL Server in any other circumstances.
As far as Visual Basic goes... Well, that depends. What are you trying to accomplish? In Query Analyzer, I use T-SQL all the time. I occasionally use the xp_cmdshell prompt to use DOS-like commands and I have, only once, ever needed to use VBScript / ActiveX script in a job and that is to copy backup files over the network to another server.
What you use and when you use it depends entirely on what you need SQL to do. If you can get everything done in T-SQL, by all means, use T-SQL. If you can't, that's when you start using VB (and C# in SQL 2k5).
Does that help or did I just confuse you more? If the later, please explain exactly what your situation is so we can try to help better.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"