>>Tim,
>>
>>You bring up a good point about SQL Server location. I believe it will be on the same network but where, I don't know yet. I presumed that I would be able to connect to the SQL Server directly. I don't even know what to ask the customer IT manager to find out what type of connection I could have to the SQL Server. I would prefer not to use Web Service for the simple reason that I know nothing about it. And I am trying to make this project to work as simple as possible. My web applicatin is very simple. It has in essence 2 features: 1 - user enters data on a page and the Submit creates a record in a table. 2 - user enters a key value and gets to see the status of the record. The record itself will not be updated by the ASP.NET application (after initial insert) but by a VFP application. The VFP application, btw, will be communicating with a Pocket PC (sending the data back and forth in the form of XML files). As far as a framework, I will probably not use one; at least in the first phase of this project (of course, if customer approves it).
>>
>>As to Stored Procedure, do you suggest using SP because it is faster or easier to maintain? My approach (again maybe not so accurate since I don't have much experience) was going to be not to use stored procedures. The reason, I thought, that I will have more control/access to the ASP.NET application than to the SQL server. And if there is a bug or something need to be changes quickly I could do it in the ASP.NET and not to have to go into database to update a stored procedure. Again, maybe this is because I have not worked much with stored procedures and not really sure how to do it right.
>>
>>Thank you for your input.
>>
>>
>I can only answer regarding SP - it would be easier to fix the logic in SP than in direct SQL statements in the page (you would then need to modify the pages).
>
>Having SP makes at least an attempt of separating Data Logic from Presentation Logic.

Thanks