>>>Does anyone have a suggestion on how to handle date (as opposed to date-time) fields on SQL-server, using SQL-pass-through?
>>
>>What about a remote view. That'll allow you to map the date/time to a date field.
>
>Well George, I tried that and it seems to work. So maybe it's the solution I need. Although I thought that George Simon's idea was interesting too.
>
>So here's my next question: (I'm really a pest, eh?) If FOXPRO can do that with views, why can't I do that with SQL pass-thru? What is FoxPro doing?

The easiest answer to this is run GENDBC against the database. That will create the code necessary to generate both the database and the view. The short answer is that a CREATE SQL VIEW statement is used, and DBSETPROP() is used to define the incoming data type.

>In a different message you told me that you once traced the ODBC calls FoxPro made to learn how FoxPro did some things automatically. How do you do that? I started ODBC logging, but couldn't make head nor tail of what was in \SQL.LOG. There's also the Visual Studio Analyser, but I don't know where it writes its stuff nor how to get it out.

I'm not sure. The only time I can recall doing anything like this was that I was having a performance problem with an ODBC data source. I "traced" the problem to the fact that I had inadvertantly turned the logging feature for the SQL statistics. When I turned it off, the problem went away. Just a case of a little detective work.< s >

>BTW, I used your LNKFILES.DLL. It worked great. Thanks!

Thanks for the kind words. It's always nice to get feedback (especially positive< bg >).