Graham Brown (CompSYS) wrote:
> Hi all
>
> I have a bit of problem with a system which I can't get my head around and
> wonder if anyone can do me a sanity check.
> What I have is two tables arranged in header/detail fashion. The key field
> between the two is a job number
>
> Header table stru i
> > Thanks! Yep. This is effectively what I'm doing with the cursors.
> > Was trying to work out if I can do this another way due to the speed of the
> > thing.
> I've worked with systems that only created the top level before
> displaying the cursor, and stuffed a dummy record into the branches t
On 4/19/07, Graham Brown (CompSYS) <[EMAIL PROTECTED]> wrote:
> Thanks! Yep. This is effectively what I'm doing with the cursors.
> Was trying to work out if I can do this another way due to the speed of the
> thing.
I've worked with systems that only created the top level before
displaying the c
33
To: ProFox Email List
Subject: Re: Self referencing joins
On Apr 19, 2007, at 12:30 PM, Graham Brown ((CompSYS)) wrote:
> With the application I can easily go 15 levels deep due to the way my
> customer sets up how they build things
>
> What I need to do is get this info into
On Apr 19, 2007, at 12:30 PM, Graham Brown ((CompSYS)) wrote:
> With the application I can easily go 15 levels deep due to the way my
> customer sets up how they build things
>
> What I need to do is get this info into a cursor so I can populate a
> treeview with it, I currently create cursor_leve
Hi all
I have a bit of problem with a system which I can't get my head around and
wonder if anyone can do me a sanity check.
What I have is two tables arranged in header/detail fashion. The key field
between the two is a job number
Header table stru is for the sake of argument
Jobno
Product to b
6 matches
Mail list logo