>Hi there,
>
>There's a data entry screen that a coworker is writing using .NET (I think 2010 or maybe 2014 64 bit). He's running into issues b/c this particular table has IDX files associated with it, so because of this problem we are creating a foxpro com object to take care of reading and writing to the table. Fist question is if there is a work around to the IDX issue? This would save us from writing the foxpro com object, also is there a better approach than the foxpro com object?
>
What is stopping you from moving from idx to cdx ?
ODBC also might support opening older index files, dunno how far you went into docs...