>I'll first start off by saying that my requirement of creating a Crystal report off of our database is bringing this issue to light.
>
>The core problem is that the ODBC driver does not recognize a table which has an auto-incrementing field. I can't create the report using the OLEDB provider to access the data, because if I select that driver, the Crystal Reports Designer will crash consistently every single time.
>
>Does anyone know if anything is being done to address these two issues or do I have to submit something?
>
>Laterness,
>Jon
Pressumably, the ODBC driver accepts older data formats.
One solution would be to search for a newer ODBC driver.
Also, in VFP, you could try to copy to a table with the old structure.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
