The VB Connection has DATABASE=HOMAG so that is setting your current database (schema). The ABL connection isn't doing that or setting the DefaultDatabase property.
That is why you have to prefix the tables with the database (not always a bad thing imo).
Every time you read a record in the 4GL (unless you use the tablescan option or look up by ROWID/RECID) you are reading one or more index entries.
The very high level process is as follows... the 4GL reads the appropriate index blocks as well as it can based on the where clause and existing...
Glad it helped. Depending on a lot of version specific things (.NET, Driver, etc) connection pooling can be enabled by default. This just tells .NET that you are done with that connection with no plans to reuse it.
That certainly isn't all of your code... missing a few details like the datareader :-)
Adapt the code for your environment and see if the behavior still exists Progress KB - SQL: Sample VB.NET code to establish a DSN-Less ( DSNless ) ODBC connection to an OpenEdge database.
See this KB for an explanation of how to set the proper parameters to make sure all of your tables and indexes are being tracked.
Progress KB - How to verify if the current values of -basetable -tablerangesize are sufficient for the current schema?
That would be a strange error to get while already connected to the database. Is your program trying to reconnect to the DB or a different DB?
Is the dump procedure running from a scheduled task as a different user than you are logging in as?
The first error is a permissions or path issue... the second error means that your environment variables/INI file settings are wrong and it can't find the DLL file.
Do manual connections work?
Incremental backups in OE take about as long as full backups and are almost useless when it comes to restoring.
No images, clobs or blobs in the database. I agree that 1TB is extreme for most OE shops... but virtually nothing for a large business Multi TB databases are extremely common these...
When your databases get above 1TB... probkup becomes much less useful and OS backups become the realistic choice. If your database is 200GB or smaller probkup is the sane choice.
If they would only multithread (or vastly speed up) probkup it would be a much better option for larger databases.
See this KB Progress KB - Getting error 3624 running _progres.exe on windows
Short version... make sure you are using the GUI client and not the CHUI client.
If you are trying to do this as part of your application and not a mass data fix... then look into the SUBSTITUTE function instead.
If you are trying to do a mass data fix... you would need to use multiple/nested replace statements with all of the variations of word breaks.. and a lot of...
A lot of how you do it depends on your application and how users connect. If the users are logging in through CHUI/Terminal access you can change your script to make the file name/path based on their user id or home directory. Something like -clientlog $HOME/client.log or -clientlog...
It is pretty accurate except for certain errors thrown by dynamic queries/objects from time to time.
Keep in mind that this will increase the write activity to disk... depending on which log entries you enable. And you would want to have a unique log file path for different users of your...
Two KBs to help:
Progress KB - How to turn on 4GL tracing within WebSpeed, AppServer and the 4GL Client?
Progress KB - What are the possible values for the -logentrytypes startup parameter in OpenEdge
If you are running an interactive application you should be able to use -debugalert and you...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.