150k tables are actually rather small... I believe his 150MB tables are just a little bit bigger. :)

-Michelle

>Hi John,
>
>I see that Josh W. has given you some possibilities. Not having experience with them myself, I cannot elaborate further except to say that Josh's suggestions have always been sound.
>
>Based on what you've said here I would have guessed that continuing as you are so far would work well - I don't think that 150K tables is huge by any means.
>
>Good luck,
>
>Jim N
>
>>>John,
>>>
>>>While learning details on VFP/SQLServer development is no doubt a good thing for the longer run, "several offoices across the country need access to my application" is not necessarily a good reason to have to step into that arena.
>>>
>>>If you are using this as an excuse to get into SQL Server, then by all menas, I hope you get the answer to your question. But if you want to determine the actual "need" to go that route, maybe more details will provide for more discussion leading to a different decision. It might also lead to precisely where you are headed.
>>>
>>>good luck,
>>>
>>>Jim N
>>>
>>>
>>>>I'm completely unfamiliar with SQL Server and have not done any Client/Server development, but now I may be forced to do so because several offices across the country need access to my application. My basic question is what is the best source of information for VFP/SQL Server development?
>>>>
>>>>Thanks.
>>>>
>>>>John
>>
>>
>>Hi Jim, thanks for responding
>>
>>Here's the deal. I have built a multi-user file server based app that controls membership and marketing data. All of the data is located on my NT Server and the app is lauched be each user from their local PC. We are connected to several other sites via WAN (partial T1 384k or so). The tables are quite sizeable 150MB and up with some smaller lookups as well. This apps main purpose is to mail contracts and letters and to track membership information. What would be the best approach to allow access to users in other sites that are connected to my network? I've played a little with Citrix and haven't ruled that out yet, but as you said, learning SQL Server is "a good thing for the longer run". I respect your opinion as well as many other seasoned programmers opinions here on the UT, and would ask you how might you approach something like this. Though I would like to learn more about C/S, now is not the best time for me to hunker down and learn another product.
>>
>>regards,
>>john.