 | |
#11
 
| |||
| |||
|
Re: Using OCONV('','U50BB') in CALLX -
06-20-2006
, 12:09 PM
#12
| |||
| |||
|
|
FYI, I placed the OCONV in my CALLX trigger and here was the result: 101 CLIFF$74$ TEST 101 is the port the CALLX ran on TEST is my account CLIFF$74$ is my user id and port number my process was on. Hope this helps in the future. |
#13
| |||
| |||
|
|
"Tony Gravagno" <g6q3x9lu53001 (AT) sneakemail (DOT) com.invalid> wrote in message news:998e9297kldi8ktc7m56rve76t4pnu3e0q (AT) 4ax (DOT) com... Sholom, not sure what's going on with your system but here are a couple thoughts: [SNIP] Maybe I just had a major brain fart and just don't remember how that stuff works, so please take this all with a grain of salt. Triggers have been notoriously unstable in earlier versions of D3NT and there have always been problems when trying to process data with triggers between the VME and FSI.... Sorry I can't be more helpful. T I use triggers and indexes all the time. I use soundex a lot, so I usually have a trigger to convert the plain text to soundex fields which are then indexed. All our web pages depend heavily on indexing to reduce query times to minimums. I have a routine that locates dealers within a variable number of miles from the users zipcode. That uses an index of latitudes/ Sholom, maybe this is really what you want. From D3 Ref: x correlative x type ac(v) provides an audit trail for items that are updated. type specifies the type of stamp to use, and may be any of the following choices: "a" places the name of the user in the specified attribute when the item is filed. "d" places the current date in the specified attribute when the item is filed. "s" adds the total time (in seconds) the item was in UP into the specified attribute. The value is cumulative. Each time the item is updated, the current usage is added to the previous time. "t" places the current time in the specified attribute when the item is filed. "ac" specifies the attribute count into which the stamp is to be placed. "v" specifies that each time the item is filed, the stamp is to be inserted as a new value. If "v" is not specified, the current stamp overwrites the previous entry. The "v" has no effect with the "s" option. The audit stamp codes may be combined into more complex expressions, such as "xa1d2s3v". This example will stamp attribute 1 with the user, attribute 2 with the date, and attribute 3 with the time, adding subsequent stamps as multi-values. When stamp specifications are combined, the system will not add another stamp if the user and date are the same. For example, if a stamp already exists for user 'dm' on 09/28/94, and the same user updates the item on the same date, another stamp will not be added. This does not apply when specifying stamps separately. Examples: 1) xa14 This places the user-id in attribute 14. 3) xa3d4t5 This complex expression adds the user-id in attribute 3, the current date in attribute 4, and the current time in attribute 5. Mark Brown |
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.