Aller au contenu principal

Recherche

Recherche

Error #3200 No Records Found

Commentaires

5 commentaires

  • Avatar
    Legacy Poster

    We have the exact same issue in 2016R2 Automation Edition on just two of our labels.  It seems to add extra characters around the query prompt.  Other than making the file read-only and having the users exit the program I have not found a solution yet either so I am hoping one of use hears something.

    0
  • Avatar
    AQUARELLE INDIA

    i am having the exact issue in version 10.1 sr4.

    0
  • Avatar
    Peter Thane

    I saw something similar at a customer's where a newer version of an ODBC driver was sending through extra none printable characters (spaces) that older ones stripped off and this was messing up the data that BarTender was receiving and so we had to edit the database to make sure these characters were removed.

    0
  • Avatar
    Charles Isaac-Samuel

    Generally, the error message "no records found" means just that and can't find any matching records being queried for. The most common scenario people run into if it browses correctly in the database connection setup but not at print time is the query records selection is not set correctly under the file->print dialog. Make sure it is set to all records if you are trying to query from all records on the database. --Jasper Wen

    0
  • Avatar
    James Palmer

    Hey all

    Helpful hint. If you are adding prefix/suffix's to the named datasource, then when you have a action which updates a database after printing, error 3200 will pop up.  I created a 2nd datasource & added the prefix in there & linked it to the first datasource.

    Happy printing

    James

    0

Vous devez vous connecter pour laisser un commentaire.