Search results

This tool does the same, and more, and has a GUI: http://www.smart-it-consulting.com/smart-db-check/ Since it's still in BETA stage, you can download it 'for free'.

ASSIGN SESSION:DEBUG-ALERT = TRUE NO-ERROR. in the very first procedure will work too.

Search for 'game': http://www.4gl.fr/download.htm

Use OLD BUFFER to get the old value, then update the children in the WRITE trigger. Better redesign the crap, primary keys must not change, never.

Progress related books: http://www.smart-it-consulting.com/catindex.htm?node=34

I was sick on producing individual reports, so I developed a more generic approach: The Smart Data Pump is an add-on for the Progress® ADM2 framework. Feed it with the handle of any smart data object and it produces user defined reports in various output formats. The plug-in process is...

If POST is not suitable (e.g. no forms - no buttons) use GET in links <code> <A HREF='http://www.yourdomain.com/.../nextPage.htm?variable1=value1&variable2=value2&dbuser=jeff' TARGET='_self' TITLE='Continue'>AnchorText</A> </code> BTW you can use GET in forms too, this enables back buttons...

... and optimize RPB (records per block) for each table and put all indexes in 1RBP areas.

My list of Progress related books may get you started: http://www.smart-it-consulting.com/catindex.htm?node=34 HTH

http://psdn.progress.com/library/webspeed/index.ssp http://www.innov8cs.com/products_books.asp http://www.progress.com/progress/products/documentation/docs/webspeed/gsw/gsw.pdf

Repost http://www.progresstalk.com/showthread.php?t=72575 {&SELF-NAME} contains the variable. E.g. in the VALUE-CHANGED trigger put IF SELF:TABLE <> 'RowObject' THEN ASSIGN {&SELF-NAME} NO-ERROR. or ASSIGN SELF:PRIVATE-DATA = ? SELF:PRIVATE-DATA = (IF SELF:TABLE <> 'RowObject' THEN...

Sequences are meant to produce technical keys, which are mostly invisible to users. They aren't reset if a transaction fails. If you need consecutive numbers, e.g. invoice numbers, you need to increment an integer attribute of a table within the transaction.

Depends ;) If the number of unique values per sequence is a concern, I'd go for UUIDs. Actually, each sequence can generate 4 billion values (-2147483648 to 2147483647) while the limit per table is 2 billion tuples or 256 gigs. Thus, if you use one sequence per table, usually you won't run out...

Create a sequence with the data dictionary, then, in your create trigger, you assign the value to the primary key: ASSIGN Table.PrefixID = NEXT-VALUE(SequenceName).