W
Warren Ayen
About a year ago my boss had me start writing our own mfg application. Since
I didn't have time to learn ADO, I used DAO instead, in Visual Basic .NET.
Since I'm not using ADO.NET, I need to be able to start Access 2000 from my
software (referred to as Unified) and then display various reports. I
accomplish this by writing a small text file (just one line) to the root of
the drive, then opening up the database and supplying the password/username.
In the database is a macro called "AutoExec" that runs a subroutine that
reads the file, parses the command, and opens the report needed. Sometimes
the command will include further information, such as the specific ID of
whatever is to be viewed in the report.
My problem is this: most of the reports, for some reason, when run through
the macro, will not display. I'll be told by Access that there is no data. If
the report does load (by me using "On Error Resume Next", the report will be
blank. This happens with about 90% of the reports. What is really frustrating
is that I can open the report up myself (by double-clicking it), and the
report will run just fine, or if I create a new form, put a button on it, and
run the same damm code that the text file is asking for the report will also
run properly. Alternately, a prompt in the report (such as a mistyped field
in the SQL statement) will also make it run properly.
One particular error is when the Aged Trial Balances report is run. For some
reason, if run through the macro (ie, unattended), it will display all of the
detail lines for the Customer except for one. Just one line, randomly
vanishes, which means if there is only one line, the report comes up blank.
Two lines, I get one, three lines, I get two, and so on. If I open the report
myself, everything is fine. There is nothing particular about the line it
drops (for instance, one time it dropped line 3 of 4)
This is beyond frustrating. We are ready to roll the sofware out in less
than a week and I need this fixed.
(ps, if you are planning on suggesting switching to ADO.NET, don't waste my
time).
I didn't have time to learn ADO, I used DAO instead, in Visual Basic .NET.
Since I'm not using ADO.NET, I need to be able to start Access 2000 from my
software (referred to as Unified) and then display various reports. I
accomplish this by writing a small text file (just one line) to the root of
the drive, then opening up the database and supplying the password/username.
In the database is a macro called "AutoExec" that runs a subroutine that
reads the file, parses the command, and opens the report needed. Sometimes
the command will include further information, such as the specific ID of
whatever is to be viewed in the report.
My problem is this: most of the reports, for some reason, when run through
the macro, will not display. I'll be told by Access that there is no data. If
the report does load (by me using "On Error Resume Next", the report will be
blank. This happens with about 90% of the reports. What is really frustrating
is that I can open the report up myself (by double-clicking it), and the
report will run just fine, or if I create a new form, put a button on it, and
run the same damm code that the text file is asking for the report will also
run properly. Alternately, a prompt in the report (such as a mistyped field
in the SQL statement) will also make it run properly.
One particular error is when the Aged Trial Balances report is run. For some
reason, if run through the macro (ie, unattended), it will display all of the
detail lines for the Customer except for one. Just one line, randomly
vanishes, which means if there is only one line, the report comes up blank.
Two lines, I get one, three lines, I get two, and so on. If I open the report
myself, everything is fine. There is nothing particular about the line it
drops (for instance, one time it dropped line 3 of 4)
This is beyond frustrating. We are ready to roll the sofware out in less
than a week and I need this fixed.
(ps, if you are planning on suggesting switching to ADO.NET, don't waste my
time).