>>It's not a *real* table Gene, it's just a representation of a table within
>the model.
>
>Ohhh .... I wouldn't think Microsoft would have soldl me products (NT
>Workstation, SQL Workstation)
>that I didn't really need it. <g>
>
>>I wont be able to get the model to generate the physical tables until I
>get my SQL Server setup.
>>I'll let ya know about the answer to the buggy ODBC problem when I hear
>back from xCase.
>
>Thanks ... ODBC errors are always tedious to figure out.
>
>BTW: NT Server has event tracking that you can turn on for ODBC connections
> but it can throw out thousands of lines that I don't even M$ understands.

Hmmm... never thought about Event Tracking. So I still dont know about that stupid Jet Error I was getting, but I know why I couldnt do what I wanted to. Seems that the current version of xCase Pro doesnt support multiple DBMS types except for mixing and matching different flavors of Fox in one model. Next version due out in May will, but for what I need done now I have to create a VFP model, bring in my 2.6 tables and redesign, then generate the VFP DBC and upsize the sucker into SQL Server and then re-engineer a new SQL model. (huge sigh) I always get stuck with the hard way to do things :)

And thanks again for your input Gene, I thought I was losing my mind yesterday. BTW, what is the difference between User DSN, System DSN, and File DSN?