×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

PEStartPrintJob : Error detected by database DLL.'

PEStartPrintJob : Error detected by database DLL.'

PEStartPrintJob : Error detected by database DLL.'

(OP)

I get this error frequently. I'm using Info 7.0.2.0, it's running as a service on NT4.  The database is btrieve/pervasive:

PEStartPrintJob : Error detected by database DLL.

All the reports are being sent to email (MAPI)

Sometimes the reports run fine if I refresh them in designer, but not always.  The same report will run fine one day and then fail the next, always with this same error.

We are going to upgrade to Enterprise, but after reading some of the posts here, it looks like a may be stuck with Info a little longer than I thought.

Any ideas as to what is causing this error?

Thank you
VE

RE: PEStartPrintJob : Error detected by database DLL.'

Nice generic message, huh?  A slightly better error message would be "The parameter value passed to the database is either unrecognizable or is in an unexpected format".  

In my experience, this error message occurs with parameters.  Perhaps the parameter being passed was in an incorrect format?  This is the standard message, for example, when one of my users schedules a report with an incorrect date parameter (ex:  not "date(yyyy, mm, dd)" format.  I hope this helps...

RE: PEStartPrintJob : Error detected by database DLL.'

(OP)

Thank you.  This is interesting.  The database I'm using stores dates as numbers, all of the date fields I use for parameters are actually formulas:

pwformatdate({table.field})

All of my date parameters are {@date}=today or
{@date}in monthtodate

I can't remember the last time a report without a date parameter failed... So this could be it.  I'm not sure what to do with this though. Changing the date format sounds confusing.  Any ideas?

Thank you
VE

RE: PEStartPrintJob : Error detected by database DLL.'

VE: There is a UDF available to convert Btrieve/Pervasive numbers to dates and vice versa. Drop me a line if you need it. I agree with rhinko that this could be the problem.

David C. Monks
david.monks@chase-international.com
http://www.chase-international.com
Accredited Crystal Decisions Enterprise Partner

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close