From: genew@ocis.net   
      
   On Wed, 28 Jul 2010 00:05:28 +0200, Erland Sommarskog   
    wrote:   
      
   >Gene Wirchenko (genew@ocis.net) writes:   
   >>      I did not say that there was. Maybe, that could be the first   
   >> answer.  Start with your paragraph and then add 'If you are planning   
   >> to develop with Microsoft SQL Server, then see the section/manual   
   >> "Microsoft SQL Server - Getting Started - for Developers"' and so on.   
   >   
   >And then you would only tell me that is none that fits you. And you   
      
        You are right in your later comment that you do not read minds   
   well.  I share your difficulty.   
      
   >would probably be right. Judging from some other posts I have seen   
   >from you, you are probably better equipped to start working with SQL   
   >Server than many other newbies I've seen in newsgroups and forums.   
      
        That is little consolation.   
      
   >>      I do not know much about SQL Server yet.  That includes which   
   >> questions I need to ask.  Why do you insist on making it difficult?   
   >   
   >Because parapsychology *is* difficult. I've tried for ten years to   
   >reads people's minds in SQL Server forums, but I often fail. It could   
   >certainly have helped from the start, if you had said what background   
   >you have.   
      
        I suppose so, but it is difficult to know what is needed.  Here   
   goes:   
      
        I have an in-house app written in VFP.  It uses VFP's internal   
   tables.  We now need to make it more accessible.  My boss has decided   
   to go the Microsoft route.  I now have to get going with SQL Server   
   from about zero.   
      
        A rewrite of the app is likely, but first, I have to learn enough   
   SQL Server.   
      
        Part of my problem is that I know how VFP's dialect of SQL works,   
   but I do not know how SQL Server differs.  For example, here is a VFP   
   create table:   
             create table contrived (somedata c(20), moredata n(5))   
   SQL Server chokes on the types.  I could use a list of all of the   
   types and what they are.   
      
   >>      But I have no idea how to make SQL Server work.  Yet.   
   >   
   >Download SQL Server Management Studio Express, if you have not done so   
   >already. Start it, log into SQL Server, specify (local)/SQLEXPRESS for   
   >the server name. Open a query window. Run queries. If you fail to connect,   
   >open SQL Server Configuraiton Manager, and make sure SQL Server is   
   >running. (And that the instance name is SQLEXPRESS.) If you need to   
   >connect from a different machine, it's gets a little more complicated,   
   >but we take that in another lesson.   
      
        OK, it appears that I am not totally ignorant anymore.   
      
        What exactly does "connect" mean?  If I am using SSMS on a   
   database, I assume that counts.  I am not totally sure though.   
      
        I would like to know how to connect from VFP.  I will have to   
   look up VFP particulars, but I also need to know how to connect to SQL   
   Server / Express.  What are the particulars for the latter, please?  I   
   do not know what I have to know to create a connection from something   
   not part of SQL Server.   
      
   >>      I have no idea whether that book would work for me.  What is   
   >> "Transact-SQL"?   
   >   
   >Transact-SQL is the SQL dialect that SQL Server uses. Nor do I have any   
   >idea whether that book is good for you. As I said, my psychic capabilities   
   >are limited.   
      
        I thought the name was "TSQL", or is that something else?   
      
   Sincerely,   
      
   Gene Wirchenko   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)