"odbc Is Processing The Select Statement" Querying All Records? S’abonner

0
Avatar
Legacy Poster

When I open Bartender 10.1 Enterprise, it immediately queries all records for some reason which will take a few minutes before I can do anything, at the bottom I see Record 1 of 9,541.

 I get the message "ODBC is processing the SELECT statement". I've set a limit on the server side but is there a way to set a limit within the Bartender application?

 It's too slow to be in production right now. Whenever you go to the next record it seems like it will query all 9,541 records again before going to record #2.

 

Thank you

6 commentaires

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Maybe this should be moved to the Wish List forums ... I would also like to see some kind of limit introduced.  I have a few labels which look at SQL tables that are very large and can take sometimes 15 min to open up the document.

0
Avatar
Domingo Rodriguez
Modérateur
Actions pour les commentaires Permalien

BarTender now has a live database template design, where you can basically browse through all records of the database even at design time. I'm wondering if you would still get the same delay if you turn this feature off...

 

Open the BarTender document in BarTender, and now look at the "database" bar you will see at the bottom of the template design. There is a database icon which you can click on to disable this "live database" feature. If you now save the BT document, close BarTender and reopen it, will the loading of the document still be slow?

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

It seems to help on the loading of the label but is there a way to prevent this same querying when you are messing around with the database connections?  If you are joining to a large database with multiple tables and you hit the query tab it takes a long time to respond.  I can only imagine it is doing something similar to when the label is loaded.

0
Avatar
Domingo Rodriguez
Modérateur
Actions pour les commentaires Permalien

I can tell you e.g. that our support for multi-database joins isn't the most optimal. We added a feature request in our system in order to improve this in a future version of BarTender.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

That's exactly how I am using BarTender. Our database is extremely large... Can't do anything in live design mode

0
Avatar
Domingo Rodriguez
Modérateur
Actions pour les commentaires Permalien

Rather than connecting to a main (huge) database + to one smaller database (normally a text file which will do the Join), you could instead create a query prompt on the main database and then pass the query prompt value at print time. If this an option for you crz606?

Vous devez vous connecter pour laisser un commentaire.