Re: [DUG]: Name not unique in this context'

1999-03-28 Thread Edward Huang
At 15:47 29/03/1999 +1200, you wrote: > > >1 per data module ...? > Maybe. But our app has 2 per most of data modules. Actually, we are using 2 sessions in our App which are defined in one data module. All of other data modules define datasets which are belong to one of these 2 sessions. Anyway

Re: [DUG]: Name not unique in this context'

1999-03-28 Thread pjones
bject: Re: [DUG]: Name not unique in this context' At 13:45 29/03/1999 +1200, you wrote: > > >Did you check that autosessionname is true? You can still attach the >various dataset to either session. > I learned from help that you can only have ONE session if you want to set

Re: [DUG]: Name not unique in this context'

1999-03-28 Thread Edward Huang
At 13:45 29/03/1999 +1200, you wrote: > > >Did you check that autosessionname is true? You can still attach the >various dataset to either session. > I learned from help that you can only have ONE session if you want to set 'AutoSessionName' to True. Is help lying? -

RE: [DUG]: Name not unique in this context'

1999-03-28 Thread Edward Huang
At 08:12 29/03/1999 +1200, you wrote: >Hi Edwin, > >Do you know WHY it would generate this error message when dynamically >creating table-components?? > >John. > No, we DONT KNOW. Also, we are not dynamically creating table-components in the module which creating the exception. -

Re: [DUG]: Name not unique in this context'

1999-03-28 Thread pjones
Peter Jones/Logistics&Information Technology/Christchurch/Foodstuffs) Subject: Re: [DUG]: Name not unique in this context' At 08:12 29/03/1999 +1200, you wrote: > > >This is an error that results when you havbe more than one tdatabase >connected in the same session and

Re: [DUG]: Name not unique in this context'

1999-03-28 Thread Edward Huang
At 08:12 29/03/1999 +1200, you wrote: > > >This is an error that results when you havbe more than one tdatabase >connected in the same session and the database names are not unique. Try >adding a session component to the datamodule(s) and setting auto session >name to true and on the database com

RE: [DUG]: Name not unique in this context'

1999-03-28 Thread John Christenhusz
Edwin Das [SMTP:[EMAIL PROTECTED]] > Sent: Friday, March 26, 1999 9:49 AM > To: Multiple recipients of list delphi > Subject: [DUG]: Name not unique in this context' > Importance: High > > Good day, > > We got a new exception recently. The exception says &

Re: [DUG]: Name not unique in this context'

1999-03-28 Thread pjones
dstuffs) Subject: [DUG]: Name not unique in this context' Good day, We got a new exception recently. The exception says 'Name not unique in this context'. It's probably database related, and our software using Delphi 3.02, BDE 4.51/5.01 with Paradox table. My guess

RE: [DUG]: Name not unique in this context'

1999-03-25 Thread Martin Ease
Subject:[DUG]: Name not unique in this context' Importance: High Good day, We got a new exception recently. The exception says 'Name not unique in this context'. It's probably database related, and our software using Delphi 3.02, BDE 4.51/5.01 with Paradox tabl

[DUG]: Name not unique in this context'

1999-03-25 Thread Edwin Das
Good day, We got a new exception recently. The exception says 'Name not unique in this context'. It's probably database related, and our software using Delphi 3.02, BDE 4.51/5.01 with Paradox table. My guess is that it happens when I open some tables. This exception just happened from few day