Hi,
I'm trying to write a monitoring tool which will take a flat, fixed length file (or files) and report on the findings.
I've used VBa in Access for a number of years and normally I would just import into a table, however for the VB application, there are no tables, no database.
The file will be reported to a list box and a number of readonly text fields, allowing the user to view the current status.
The best I've found to do this is to convert it to CSV and process via an ODBC link. This obviously creates a large (and probably unnecessary) overhead on processing, as the log is written to (and therefore monitored) 24/7.
I cannot change the source file, however, this file is copied locally to allow for easier processing.
Can anyone suggest a better way of reading the file and point me in a direction.
Many thanks in anticipation,
Fitz
Did you know, there are 10 types of people in this world:
* Those who understand binary
and
* Those who Don't!!
I'm trying to write a monitoring tool which will take a flat, fixed length file (or files) and report on the findings.
I've used VBa in Access for a number of years and normally I would just import into a table, however for the VB application, there are no tables, no database.
The file will be reported to a list box and a number of readonly text fields, allowing the user to view the current status.
The best I've found to do this is to convert it to CSV and process via an ODBC link. This obviously creates a large (and probably unnecessary) overhead on processing, as the log is written to (and therefore monitored) 24/7.
I cannot change the source file, however, this file is copied locally to allow for easier processing.
Can anyone suggest a better way of reading the file and point me in a direction.
Many thanks in anticipation,
Fitz
Did you know, there are 10 types of people in this world:
* Those who understand binary
and
* Those who Don't!!
