Thanks for the tip. I wasn't aware of the "disable triggers" trick.
I previously worked with an older version of Progress, before they
had database triggers, so code like that is new to me. It appears it
will allow me to fudge my way past this problem.
I am still going to keep trying to get an answer about what would
have changed in the last few weeks to make this suddently become a
problem.
Thanks again.
Mark
I previously worked with an older version of Progress, before they
had database triggers, so code like that is new to me. It appears it
will allow me to fudge my way past this problem.
I am still going to keep trying to get an answer about what would
have changed in the last few weeks to make this suddently become a
problem.
Thanks again.
Mark
--- In vantage@yahoogroups.com, "Chris Robisch" <blue.wine@...> wrote:
>
> Triggers can depend on shared variables that must be defined and
set properly. Don't know if Epicor provides how to do that in the
SDK. Also can't explain why this didn't happen until OE SP5 unless a
Vantage patch was also installed which added the new trigger.
>
> But you can disable the triggers with "disable triggers for load of
table-name.". This is dangerous obviously but you already must know
to create/maintain records with OpenEdge exactly how a user does with
Vantage to maintain its integrity.
>
> ----- Original Message -----
> From: markewhittaker
> To: vantage@yahoogroups.com
> Sent: Tuesday, July 11, 2006 8:02 AM
> Subject: [Vantage] Custom Progress Code Error
>
>
> I am running some custom progress code from the Progress
procedure
> editor. I am on Vantage 8.0 and we have the OpenEdge license. I
ran
> this same code several weeks ago with no problem, but since then
we
> have installed service pack 5 for the Open Edge product and now
when I
> run the code (which delets a record from the resource table) I
get the
> following error message:
>
> db/trg/Resource/delete.p Shared variable CUR_COMP has not yet
been
> created. (392)
>
> I put in code to define this variable and got past that error,
but then
> got another error just like it for DCD-USERID. It sounds like the
> delete.p procedure is looking for system variables that it
doesn't see.
> I talked to Epicor support who have no clue. The guy said that it
> sounded like I was not logged into Vantage. I set up the Progress
> procedure editor to be called from a Vantage menu and put options
in
> the command line to have the database already connected when you
enter
> the procedure editor. But I don't know why it worked a few weeks
ago
> and now I am getting this error.
>
> Anyone here have any ideas?
>
>
>
>
>
> [Non-text portions of this message have been removed]
>