I have a simple application working fine in MS Access with some VBA code. It reads a text file generated by another application "A", uses (Pervasive ODBC)linked tables to look up additional information (prices etc) in another application "B" and outputs a "merged" text file ready to be imported into application "B".
The requirements have expanded from the original spec (which worked fine) and I have had to include additional linked tables to look up further information. I have found it impossible to use the data from these tables (one won't even open) and, after much investigation, it seems most likely that there is a problem somewhere in the way the data is structured in application "B", and/or Pervasive ODBC, that Access doesn't like.
I have no trouble viewing the data via ODBC from other applications. The problem only occurs with Access.
I am wondering if I should try developing it in VB.NET? I realise it would be a bit of a learning curve but I would welcome that (I think) and there is no desperate urgency to get it done.
Any feedback from those more experienced than me would be most appreciated.
The requirements have expanded from the original spec (which worked fine) and I have had to include additional linked tables to look up further information. I have found it impossible to use the data from these tables (one won't even open) and, after much investigation, it seems most likely that there is a problem somewhere in the way the data is structured in application "B", and/or Pervasive ODBC, that Access doesn't like.
I have no trouble viewing the data via ODBC from other applications. The problem only occurs with Access.
I am wondering if I should try developing it in VB.NET? I realise it would be a bit of a learning curve but I would welcome that (I think) and there is no desperate urgency to get it done.
Any feedback from those more experienced than me would be most appreciated.