>The BROWSE command is very very helpful and in VS2005 a similar feature called I think 'DataVisualizer' (?) can be compared to the VFP's BROWSE command.
>Whenever you are in VS2005 debugger and move your mouse onto a DataTable, DataSet, ... a small magnifier will open this data for viewing / editing.
>
>A nice feature.

Sure, if you got the tools installed. However on a clients site, we can only expect our application to be installed. A build in command window (into the application) is handy for troubleshooting things. Troubleshooting VFP application data this way is much and much easier than when you only got a free scaled down SQL server version running without the QA and enteprise manager. In that case we have to write SQLEXEC() commands into the command window, which is far less optimal.

Walter,




>
>>>SQL Express is pretty darn easy.
>>
>>Not sure if it comes with a QA and EM, but if its not, I don't agree. No simple way to just open and analyse your data. Or even make changes to your schema if columns have deep dependencies on it.
>>
>>One product we develop, has both an SQL-server and a VFP version, and I can tell you that throubleshooting the VFP version is an order of magnitude easier than the SQL server version (Nothing beats a USE, BROWSE FOR and modify the record or column of interest right away) even if you have the QA avialable.
>>
>>And no, this does not have anything to do with experience or preference. We did not even discuss install issues and version control yet.
>>
>>Walter,
>>
>>
>>
>>
>>
>>>>
>>>>Even for road warrior scenarios ? On single user/single machine I lean to simpler solutions, on citrix/TS solutions I can argue both points.
>>>>
>>>>regards
>>>>
>>>>thomas