I have a simple report wherein I get the customer credit status from FP (a sql database) and from our accounting software SBT (a foxpro db), and compare them side by side. When I open it up and refresh the data the first time, it works fine. I had SBT running in the background, but not FP.
So then I open up FP and update a record. NOW when I go back to Crystal (SBT and FP are still open) and hit refresh, I get two error messages. The first says "DBPROCESS is dead or not enabled". The second says "Error detected by database DLL". They are both in boxes labeled "Seagate Crystal Reports".
Even when I close FP and then hit refresh, I get the error messages.
If I close Crystal completely and then reopen it and reopen the report, I get the prompt to log back into the sql server, and the report runs fine.
I reported this to the FP vendor and they said, it's probably a Crystal report problem.
Has anyone else heard of this? What's going on? How can I stop it from happening? Thanks.
Kelley
So then I open up FP and update a record. NOW when I go back to Crystal (SBT and FP are still open) and hit refresh, I get two error messages. The first says "DBPROCESS is dead or not enabled". The second says "Error detected by database DLL". They are both in boxes labeled "Seagate Crystal Reports".
Even when I close FP and then hit refresh, I get the error messages.
If I close Crystal completely and then reopen it and reopen the report, I get the prompt to log back into the sql server, and the report runs fine.
I reported this to the FP vendor and they said, it's probably a Crystal report problem.
Has anyone else heard of this? What's going on? How can I stop it from happening? Thanks.
Kelley