Search results

For starters, OE uses ":" where C# uses ".", and "." where C# uses ";".

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?

Thanks for reporting back! It's always good to know that a proposed solution worked. Future readers won't be wondering about this one.

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...

Are you asking what you need to do in a "fail over" situation to be able to replace an existing database on a PROD server with one of the TEST databases? Presumably in a situation where the PROD server has failed?

Maybe you could share some simple sample code that shows what you have so far and where you need these current buffers? I'm having difficultly understanding how it is that you are able to iterate & return them but somehow don't know what they are.

Perhaps you can share a description of the problem and your eventual solution?

Maybe. Or maybe he is testing to see if some series of operations can corrupt his configuration. I can’t tell. The steps do appear to be 90% similar to an easily found kbase for reinitializing the OEM password. But the title talks about “recovery” not initialization. So it is quite unclear (to...

And while we are at it... what version of OpenEdge are we talking about?

What is "it" and what did you expect it to do that would constitute "working"?

That is an interesting series of events. Is there a question somewhere in there?

Stefan is pointing out that "Eclipse Jetty" is used by OpenEdge Explorer. And you very likely are using that. So it is more a matter of needing to restrict access to that port because, otherwise, anyone can fire up OpenEdge Explorer and wreak havoc on your systems. (Instead of just a few...