looping thru table properties will I have to loop twice?

[sparks]

I was going to loop thru the tables and change some properties.
10 <<<<<< prp.value --prp.name = Type
False <<<<prp.value --prp.name = allow zero length
10 <<<<<< prp.value --prp.name = Type
True <<<<prp.value --prp.name = allow zero length
10 <<<<<< prp.value --prp.name = Type
True <<<<prp.value --prp.name = allow zero length
10 <<<<<< prp.value --prp.name = Type
True <<<<prp.value --prp.name = allow zero length
4 <<<<<< prp.value --prp.name = Type
False <<<<prp.value --prp.name = allow zero length

so if the type is 10 --- text field
I want to change allow zero length to true on all of them
the type is 4 --number field has me messed up
it has the allow zero lenght and its set to false but you can't set it
to true on a number field.

they type is read before the allow zero lenght
so do I have to loop thru the properties twice?
check for 10 and then loop thru again and if its a 10 set allow zero
length to true?

thanks this should have been easier than I made it (I think)

jerry

[sparks]

yep resume next is a life saver lol

thnks for the tip

jerry
On Wed, 28 Jul 2004 17:36:52 GMT, Chuck Grimsby
<c.*******@worldnet.att.net.invalid> wrote:

You can look at a property without setting it, you know. You only
need to set it when you're going to have to *do* something to it.
This means that you can look at a different property then the one
you've set (or are about to set).

Another way to deal with this would be to trap the error, ignore it,
and move on.

On Wed, 28 Jul 2004 16:23:45 GMT, sparks <sp****@here.com> wrote:

I was going to loop thru the tables and change some properties.

<snip>

so if the type is 10 --- text field
I want to change allow zero length to true on all of them
the type is 4 --number field has me messed up
it has the allow zero lenght and its set to false but you can't set it
to true on a number field.
they type is read before the allow zero lenght
so do I have to loop thru the properties twice?
check for 10 and then loop thru again and if its a 10 set allow zero
length to true?
thanks this should have been easier than I made it (I think)

[david epsom dot com dot au]

> Another way to deal with this would be to trap the error, ignore it,

In this particular situation it is likely to give you a memory leak
and slow recovery. Still, sometimes that is all you can do, and you
get the memory back when you release the database object.

(david)
"Chuck Grimsby" <c.*******@worldnet.att.net.invalid> wrote in message
news:dn********************************@4ax.com...

You can look at a property without setting it, you know. You only
need to set it when you're going to have to *do* something to it.
This means that you can look at a different property then the one
you've set (or are about to set).

Another way to deal with this would be to trap the error, ignore it,
and move on.

On Wed, 28 Jul 2004 16:23:45 GMT, sparks <sp****@here.com> wrote:

I was going to loop thru the tables and change some properties.

<snip>

so if the type is 10 --- text field
I want to change allow zero length to true on all of them
the type is 4 --number field has me messed up
it has the allow zero lenght and its set to false but you can't set it
to true on a number field.
they type is read before the allow zero lenght
so do I have to loop thru the properties twice?
check for 10 and then loop thru again and if its a 10 set allow zero
length to true?
thanks this should have been easier than I made it (I think)

--
Ability Is A Good Thing But Stability Is Even Better.