Search results

OK, I'm using 10.1A here and there's no ADM2 support for a getPageEnabled() type function. So, unless PSC have added something in newer versions, I guess you have to write one for yourself! New function in folder.w, getFolderEnabled. Returns logical, accepts one input parameter (page number...

SmartObject folder.w or Microsoft TabStrip OCX?

Even with a few hundred records, the TT solution won't be massively slow. But I don't know if it will be problematic for you - depends on where and how often it would be used in your system I suppose.

If you need to sort the string itself, populate a temp-table with one record per entry and then read it back out using an index or BY phrase. If you only need to sort the combo-box, you can set the SORT attribute of the combo to TRUE any then use list-items in any order. You can only set this...

I don't think the poster is updating any records in the browse. I think they are changing the query criteria based on the fill-in screen-value, so they need to re-open the query. If that's the case, calling a refresh() won't help here.

When you drop a browse onto a container using AB, you get a query defined automatically with the same name as the browse. So, the easiest way of refreshing the browse is to re-open the query using the new date criteria. So, after some user event ("refresh" button, leave of the date field...

Wow. That sounds like a bug in the ADM to me. I think you're on the right lines with the record sets being involved, but even with a large record set and a small rowsToBatch, I can't reproduce it here! Maybe it's been introduced after 10.1A02? Regardless, you could report it to PSC as a...

Hi there! I'm using 10.1A02 here, so my results may vary, but this approach (rowidWhere followed by a fetchRowIdent) is working fine here. If the rowid returned by rowidWhere is for the last record in the dataset, then I would message out the value in cWhere to see what where clause is being...

Blimey, what a strange requirement... You can set the toggle-boxes to be "movable", allowing the user to drag them around. Then you're left with two problems: 1. When the user drops one (ahem), you will have to run around the widget-tree in the frame and re-order the 10 toggle-boxes based...

Yeah, with extents you have to loop through them all. So this: DO i = 1 TO bh:NUM-FIELDS : PUT bh:BUFFER-FIELD(i):BUFFER-VALUE. END. becomes something like this: DEFINE VARIABLE hBuffer AS HANDLE NO-UNDO. DEFINE VARIABLE hField AS HANDLE NO-UNDO. DEFINE VARIABLE iField AS INTEGER...

Cool. If you need a quick example of a dynamic query being built, I posted one on this thread a few days ago: http://www.progresstalk.com/showthread.php?t=114705

Best solution - remove all shared variables. They are evil, and should be done away with at the earliest opportunity. There are many alternatives to their use, for example a session-level super procedure with a temp-table, get and set functions. Rubbish solution one - increase -l to...

This won't work - the include file is expanded out at compile time, and so you can't use includes to produce a flexible FOR EACH like this. FOR EACH is a static construct, and unless you want to compile-on-the-fly, you won't be able to achieve anything in this manner. You don't mention your...

I'm not sure what mechanism you're using to get the first 1000 records into the temp-table. Perhaps you could post some of the code? If you have the buffer-handle and query-handle of the TT, there's not much you can do from there really. You need to have some idea of what query was used on...

Sorry to have to tell you that it does in fact work. If you have a combo-box, cbTest: cbTest:LIST-ITEMS = "1,2,3". Then you have a button which does this: cbTest:DELETE("2"). Press the button, and the combo only has possible selections of "1" and "3". You asked how to remove a record...

You can use the DELETE() method to remove a specific item from the list-items of a combo. Or you can re-build all the items by blasting the LIST-ITEMS or LIST-ITEM-PAIRS attribute with a new delimited list.

I don't think so. I believe you have to have all the columns "searchable", or none. If you're looking for a visual cue for your users, some people add a little marker to the column label to show which ones are enabled for column-searching. Not a very elegant solution though.

Hi there! In the START-SEARCH trigger, you can refer to the browse's CURRENT-COLUMN attribute to get the handle of the column the user just tried to sort on. So, if you wanted to exclude a column called "myColumn", you could do this: DEFINE VARIABLE hColumn AS HANDLE NO-UNDO...

Sorry, but that's all I can think of! Perhaps you can add a -T to the icon, pathed to a valid temp-directory, and give the user access to this? This would then rule out the temp files being the culprit at least!

Is your code generating a file? If so, make sure the user has write access to the target dir. If this is a progress-generated file (example, sort files), check the -T temp directory. You say that the user has write access to the working directory (the "start in" directory of your icon?), but...