https://community.progress.com/s/article/P80479
Maybe you have somehow managed to connect more than one database? Does your code use CONNECT statements?
That code that you are showing is not a dynamic anything so… either the error message is erroneous or you are looking at the wrong bit of code.
Seeing the full and complete error message would, of course, be helpful. And if there are multiple errors occurring please share all of them.
If you have been waiting on the detailed schedule - it's up!!!
Prague Schedule
Boston Schedule
If you are already registered: Congratulations! You're going to have a great time and learn a TON about OpenEdge. If you're not registered: What? Why Not? What are you waiting for! Get to PUG...
No.
Adding dsrutil capabilities to the admin server commands (maybe “dsrman” or “rplman”) is similar to some long-standing enhancement requests though. For instance:
https://openedge.ideas.aha.io/ideas/OPENEDGE-I-830
Two other common reasons for an urgent need to purge data:
1) Someone thinks that it will solve a performance problem. If that turns out to be true then the real problem is the quality of the WHERE clause or the lack of proper indexes to support that WHERE clause
2) You're hiding something...
Sure, anyone with permission can delete records.
If you want to delete an entire table there is always "drop table". Performance will pretty much suck if the table is of non-trivial size.
If you know that a certain table will need to be frequently purged completely (maybe it is a "scratch"...
So you are simply trying to copy & paste the C# code into an OpenEdge editor?
Do you have any OpenEdge experience at all? Or are we starting from scratch?
What have you tried? What does you attempted translation of that code look like? And what is the nature of the "difficulties" that you are experiencing?
I cannot emphasize enough - if you are serious about working with OpenEdge, you need to attend PUG Challenge! The wealth of information and experience being shared is incredible. It is easily the most bang for your buck in the OpenEdge world. We are going to talk about old stuff and new stuff -...
One Great Conference - Two Great Locations! Prague, September 18-20 or Boston September 29 - October 2
The countdown to PUG Challenge 2024 has begun! Join us for an exciting event where innovation and expertise converge in the world of Progress OpenEdge technology. This year's conference...
The correct answer is to update to a supported version of OpenEdge and to then use OE Auditing.
You claim to be running 10.02B which, so far as I know, is not an actual release. Did you perhaps means 10.2B? (no extra "0"). OE Auditing does exist in that version, it was introduced with 10.1B...
You have added some code page conversions to one of those DLCs but not to the other. So do whatever you did to the one that has them to the one that does not. You might also want to compare $DLC/startup.pf in the two DLCs and see if there are relevant differences.
This might be a good place to...
There is no such thing as "32 bit database", there are databases that were started with 32 bit executables and there are databases that are started with 64 bit executables.
If your mpro startup parameters do NOT contain -S portNum then you are trying to connect via shared memory. In that case...
In that case your requirements for db admin and application admin are basically the same as "old PROD". I can't see why anything would change there. You might have to update your various scripts and config files to reflect new host names, IP addresses and ports and paths but that's not really a...
Databases don't have "bitness". The installed executables do.
There is no conversion of databases between 32 bits and 64 bits. There is nothing to do. You access the database with either 32 bit or 64 bit executables. If you are making shared memory connections everything needs to run from the...
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.