Recent content by Ach

As a practice, always use no-lock unless you are updating or deleting the record. For each ordercode no-lock: /* Do whatever you want to do */ End. Find ordercode where ordercode.order-code = "123" no-lock no-error. If available ordercode then do: End. Else do: End.

Thank you very much! I appreciate it !

So my knowledge about any Business Intelligence tool connecting to Progress DB is about 15 years old when there was an ODBC driver (probably called Datadirect) which had to be installed on the PC and then tools like Cognos, Crystal reports etc. were able to connect to Progress DB. Downside was...

Thanks ! The moderators seem to be too busy ;)

Correct. I mistyped. It should say create _user. assign _user._userid = "JohnDoe" _user._password = encode ("mypassword") _user.user-name = "John Doe"

No Moderators on this site?

Quite an old thread but maybe someone can benefit from this: for each _user where _userid = "JohnDoe" delete _user. end. create _user. assign _user._userid = "JohnDoe" _user._password = decode ("mypassword") _user.user-name = "John Doe" I just did this because I had the...

I did what you suggested and it says it is pending an approval from the moderator (since Friday). Do the moderators get a message automatically? Probably not so I am posting it here with the hope that they see it.

Nice to know that in the new versions, schema changes can be made in multi-user mode. Thanks and it is true that the distinction should be made between 'can' and 'used-to'.

Really? Not sure which version has that feature because whenever I make changes to the tables/fields, it always tells me that someone is connected and I can only make changes when everyone is disconnected except myself. Ours is version 10

What I meant was that you can only make changes when you are the only user connected to it. Sorry for mentioning Oracle/SQL Server

I have actually forgotten most of progress because have been doing Oracle and SQL Server since last 15 years and those DBs don't have these kind of problems and neither do they need to be in single user mode to make any schema changes.

What did you mean? That was the fix and why is it bad? Just to clarify there is a no-lock on for each For each table-name no-lock: Do transaction: create hist-table. assign hist-table.field1 = table-name.field1 hist-table.field2 =...

Thanks !