Search results

I took another look at this, and my solution does work with other tables. Turns out I was originally testing with tables that didn't have help text. :rolleyes: Thanks, Osborne!

That gives me the widget's help text, but what I want is the original database field's help text.

Progress: 10.2b SP7 OpenEdge Architect: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL OpenEdge OS: Windows 7 Professional 2009 SP1 When you set up a database field, you can assign it default help text: As the user tabs through entry fields, this help text appears automatically at...

Progress: 10.2b SP7 OpenEdge Architect: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL OpenEdge OS: Windows 7 Professional 2009 SP1 (I wish I could put that in a signature.) So after some experimentation yesterday, I figured out that by increasing the fill-in height slightly, I...

Is it possible to show the blinking cursor in a fill-in widget? If so, how? Edit: Shoot, I meant to put this under "Development." Sorry about that.

Okay, I fixed the issue by placing the popup code in a separate procedure. That way, when you click "Close" to run the trigger code "APPLY "CLOSE" TO THIS-PROCEDURE", only the popup gets closed. If you don't put the popup in a separate procedure, the trigger code of "APPLY "CLOSE" TO...

Thanks. I tried using that snippet of code with the cancel button's on choose behavior, but the button doesn't do anything when clicked. When I tried "APPLY "window-close" TO FRAME framePopup." instead, my "WAIT-FOR CLOSE OF CURRENT-WINDOW." code at the end of the program threw this error...

The popup window needed to contain a browser widget.

I want my program to do the following: If the user clicks a button, the main window will freeze and another window will pop up on top of it. If the user clicks a button in the popup window, the popup window will close and pass information to the main window, which will unfreeze. I've managed...

Oh, I see. I was thinking back to this thread: http://www.progresstalk.com/threads/_file-and-_field-tables.121950/#post-379746 But now that I've read that again, it looks like you were advising against changing the schema, not the values of _File and _Field records. My mistake!

Is it safe to change the _File table to control data access permission? Is it possible that changes to meta-schema databases won't carry over to future releases of Progress? (Sorry for reviving an old thread, but we're currently working on database security and this caught my eye.)

Thanks. I tried to do that like this: FUNCTION isSafeToReplace RETURNS LOGICAL (TABLE b) FORWARD. DEFINE TEMP-TABLE newSPQMasterLookup LIKE SPQMASTER. FIND newSPQMasterLookup WHERE newSPQMasterLookup.SPQ-NUM = " " AND newSPQMasterLookup.CUST-NUM = "1000" NO-LOCK NO-ERROR. DISPLAY...

Progress: 10.2b SP7 I've found plenty of threads about passing temp-tables to procedures but none (so far) about passing to functions. Is this possible? Do you have to pass your temp-table's buffer or handle instead?

I think I figured it out! Here's the code: DEFINE VARIABLE hTest AS HANDLE NO-UNDO. DEFINE TEMP-TABLE test BEFORE-TABLE before-table-name FIELD columnNum AS INTEGER FIELD prod-code LIKE PRODMSTR.PROD-CODE INDEX myIndex IS UNIQUE columnNum ASCENDING. DEFINE BUFFER bTest FOR TEMP-TABLE...

Thanks, Tom. This is what I tried: define variable hTest as handle no-undo. DEFINE TEMP-TABLE test BEFORE-TABLE before-table-name FIELD columnNum AS INTEGER FIELD description LIKE ITEM.DESCRIPTION FIELD prod-code LIKE PRODMSTR.PROD-CODE INDEX myIndex IS UNIQUE columnNum...

Is it possible to automatically increment a field in a temp-table whenever you create a new record? In normal tables, you have to use a trigger, so can you use triggers with temp-tables, too?

Thanks. I'd prefer not to use an external text file, though. Can I treat the value of a character variable just like the contents of a file?

I want to populate a reference temp table with hard-coded information: CREATE glConverter. glConverter.gl-num = "40101". glConverter.prod-code = "30101". RELEASE glConverter. CREATE glConverter. glConverter.gl-num = "40102". glConverter.prod-code = "30102". RELEASE glConverter. CREATE...

Oh no, that's plenty. :D It's just good to know all the reasons, especially when I'm simplifying decades old code that never used temp-tables (or arrays in some cases!) before. Knowing why temp-tables are usually the best choice makes me feel better about overhauls.

I've heard it's better to use temp-tables than arrays, but what are some reasons why? I can think of a couple (easier access to data and not needing to worry about extents or out of range exceptions), but what are some others?