Re: trigger program and ODBC

[booth@xxxxxxxxxxxx]

That is a good idea.  I am going to use the idea but in a different place. 
 Thank you.

The ODBC connectivity problem turned out to be a problem with upper/lower 
case.  The error message had been misread and a conclusion had been leaped 
to.  When I finally saw the actual message it became fairly clear. 

Sorry to trouble everyone but in a way I'm glad I did because I'd have 
never made the connection of getting the qualifying library name from the 
program data structure.

_______________________
Booth Martin
Booth@MartinVT.com
http://www.MartinVT.com
_______________________




John Earl <johnearl@400security.com>
Sent by: owner-midrange-l@midrange.com
07/01/2000 07:51 PM
Please respond to MIDRANGE-L

 
        To:     MIDRANGE-L@midrange.com
        cc: 
        Subject:        Re: trigger program and ODBC

Booth,

Are the trigger program and the file expected to reside in the same 
library?

If yes, you could query the program status data structure for the 
program's
library, and then use that name to qualify the file name.  This allows you 
to
qualify without hard coding a library name.

HTH,

jte



booth@martinvt.com wrote:

> Here is the situation:  There are two header files(Hedr1 and Hedr2) and
> their detail files (Det1A, Det1B, and Det1C) and (Det2A, De2B, and 
Det2C).
>  These files are all available to users through Microsoft Access.
>
> There's a Trigger program that changes appropriate fields in the detail
> files when the Header field is changed.  This all works well when a 
record
> is changed with DFU but not through Microsoft Access.  The error 
indicates
> a library list issue.  That makes sense to me.
>
> The idea of qualifying the file name with a hard-wired library name in 
the
> trigger program is unappealing.  How have others solved this, or am I
> solving the wrong problem?
>
> _______________________
> Booth Martin
> Booth@MartinVT.com
> http://www.MartinVT.com
> _______________________
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
david@midrange.com
> +---

--
John Earl                               johnearl@400security.com
The PowerTech Group                     206-575-0711
PowerLock Network Security              www.400security.com
--


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---




+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---