- Posts: 16
Non Specific Error Encountered
- Keith Weatherhead
- Topic Author
- Offline
- User
Less
More
6 years 3 months ago #3473
by Keith Weatherhead
Non Specific Error Encountered - Post(3473) was created by Keith Weatherhead
Greetings,
I got an error while trying to process a small DBF file to SQLITE.
Unfortunately the error message provides very little info for me to know what is wrong...
Is the error on the READ or WRITE side? What does FlowHeater not like about the situation?
Could error messages be a bit more descriptive?
Regards,
Keith
I got an error while trying to process a small DBF file to SQLITE.
Unfortunately the error message provides very little info for me to know what is wrong...
Is the error on the READ or WRITE side? What does FlowHeater not like about the situation?
Could error messages be a bit more descriptive?
Regards,
Keith
Attachments:
Please Log in or Create an account to join the conversation.
- FlowHeater-Team
- Offline
- Admin
6 years 3 months ago #3474
by FlowHeater-Team
Best wishes
Robert Stark
Replied by FlowHeater-Team on topic Non Specific Error Encountered - Post(3474)
Hi Keith,
The reason why is quite simple. On the READ side ( OleDB Adapter ) in your dBase table the column “description” are not exist You just have to read the table schema again and you should see the available fields in your dBase database table.
The error message in this case could be indeed a bit more descriptive. Responsible for this is the used OleDB datasource provider “Microsoft dBASE Driver”. Usually the thrown error messages are more helpfully In this case FlowHeater just displaying the occurred error message.
I´ll will try to find out a way to check the defined field names with the available table names in a further version.
The reason why is quite simple. On the READ side ( OleDB Adapter ) in your dBase table the column “description” are not exist You just have to read the table schema again and you should see the available fields in your dBase database table.
The error message in this case could be indeed a bit more descriptive. Responsible for this is the used OleDB datasource provider “Microsoft dBASE Driver”. Usually the thrown error messages are more helpfully In this case FlowHeater just displaying the occurred error message.
I´ll will try to find out a way to check the defined field names with the available table names in a further version.
Best wishes
Robert Stark
Please Log in or Create an account to join the conversation.
Time to create page: 0.254 seconds