Invalid File Name
I had a form-based report server running as a Windows service on my Windows
2000 Server with 6 or 7 reports that were working. I decided to change the
location of the database tables (Paradox). I changed my alias path in
Database Desktop and deleted the .NET file and all lock files from the
database directory. I deleted the old directory where the tables used to
reside. My RBServer program starts up fine, but when I go to access a
report, I get the AutoSearch parameters prompt, but when I enter the search
parameters and click OK, I get an error message saying "Invalid File Name -
Report Templates\Paid Out Report EDBEngineError, Invalid file name". I get
this error whether I request the report from a thinClient application or
through a web browser. I've removed all but 1 report from the server
program, but still no luck. Any ideas what I might have broken?
Thank you.
2000 Server with 6 or 7 reports that were working. I decided to change the
location of the database tables (Paradox). I changed my alias path in
Database Desktop and deleted the .NET file and all lock files from the
database directory. I deleted the old directory where the tables used to
reside. My RBServer program starts up fine, but when I go to access a
report, I get the AutoSearch parameters prompt, but when I enter the search
parameters and click OK, I get an error message saying "Invalid File Name -
Report Templates\Paid Out Report EDBEngineError, Invalid file name". I get
this error whether I request the report from a thinClient application or
through a web browser. I've removed all but 1 report from the server
program, but still no luck. Any ideas what I might have broken?
Thank you.
This discussion has been closed.
Comments
Try to open the report form and run the report at delphi design-time.
Try to get the one of the form based reports working in a standard Delphi
application (i..e not a server application).
Make sure that the server is running the newly built .exe and not the old
one. Brind the server down and delete the old .exe. Then copy the new .exe
to the appropriate directory.
I have experienced cases in which the paradox file path is too long, the BDE
does not work properly.
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com