Hi All

I have seen the odd 'issue log' on this one which claims it happens in D3, but not D2. I am currently using D5 and code that used to work in D3 now gives the problem.

Basically I am trying to add a master and 2 Aux passwords to my paradox tables and i use these to give different types of access (including a read only mode when the demo license expires). I use the example DBiDoRestructure code from the web site, first adding the master password, then one aux password followed by a second aux password. The code used to work in D3 but since going to D5 and BDE 5.11 I find that the second call to add an aux password removes the first one. On the BDE issues log (ref 141) it suggests using 1 instead of True, but the example does tis already. Anyone encountered this (and got round it)?

Thanks
John

Yes

No

(sorry)

Mike
--
Mike Best Programming
Brisbane
Australia

news:3ba8645a$1_2@dnews...
but not D2. I am currently using D5 and code that used to work in D3 now
gives the problem.
tables and i use these to give different types of access (including a read
only mode when the demo license expires). I use the example DBiDoRestructure
code from the web site, first adding the master password, then one aux
password followed by a second aux password. The code used to work in D3 but
since going to D5 and BDE 5.11 I find that the second call to add an aux
password removes the first one. On the BDE issues log (ref 141) it suggests
using 1 instead of True, but the example does tis already. Anyone
encountered this (and got round it)?

In article <3ba8645a$1_2@dnews>, j...@pswl.demon.co.uk says...
Yes, before adding the new password, read the existed. Finally add all
passwords (the existed and the new)

-------------------------------
Paul Lambadaris
Delta Singular S.A.
mailto : p...@singular.gr
www    : http://www.singular.gr

Thanks Paul

I got there in the end, the one thing that delayed me was in the help that comes with D5 it doesn't mention that the pecrSecOp element of the CRTblDesc record which you fill with the password info is an array and you need to specify an operation type for each password! Obvious really when you think of it, and even more obvious when you look in the BDE.int file which is more explicit.

I would put my code up here but it isn't finished - but if anyone is interested, try taking the AddAuxPassword code from the web site and simply make both SDesc and crType arrays instead of simple variables. Then initialise the arrays in the same way as in the example. In my case I was adding 2 passwords at one time anyway so i didn't need to read the existing data, but for a generic AddAuxPassword routine to work it appears you should read all the passwords that exist, populate the arrays with the relevant info and then add one more populated element to each array for your new password before calling DBIDoRestructure.

John