What is the type of your calculated password result?

-bd

The calculation result is text.

Try doing a find on each of them individually and see if you find more than one record.

-bd

When I search for each text string separately, only one record is returned, yet when "!" is entered in the field for a search, both records are returned.

Is the calculation stored or unstored?

I have a problem. I made a database to generate random passwords. The password field is a calculation adding eight letters picked by the calculation--Round(Random* 26, 0), this then is used to select a letter from the text string consisting of a...z. Just to check, I searched for duplicates and found two, but they aren't duplicates (qdgnnfkh, jrvqjrki), they aren't even close. Does anybody have a clue as to what is going on here?

The "Password" field is indexed (because of the search). The calculation is as follows:

Right(Middle(alphabet, space1, 1) &

Middle(alphabet, space2, 1) &

Middle(alphabet, space3, 1) &

Middle(alphabet, space4, 1) &

Middle(alphabet, space5, 1) &

Middle(alphabet, space6, 1) &

Middle(alphabet, space7, 1) &

Middle(alphabet, space8, 1) &

Middle(alphabet, space9, 1), 8), result is text.

The fields "space1" through "space9" are not indexed, but the "Do not store..." check box is unchecked. The calculation for these fields are as follows:

Round(Random* 26, 0), result is number

The "alphabet" field is not indexed, but the "Do not store..." check box is unchecked. The calculation is as follows:

"abcdefghijklmnopqrstuvwxyz", result is text

I know there is a better (more efficient) way of doing the field, but I don't think that would explain how "qdgnnfkh" and "jrvqjrki" can be returned as duplicates, yet when searching for each individually, only one is returned.

I suspect that the index in your file is corrupt. Try recovering the file, and see if the problem goes away.

BTW, your random function will produce values in the range of 0 to 26, not 1 to 26. You should change it to:

Round(Random * 25,0)+1

[ October 03, 2001: Message edited by: BobWeaver ]

1. Thanks, that did it

2. Thanks for the calculation

3. How can you tell when the index gets corrupt, nothing out of the ordinary happened to the file. I wasn

From my experience, the only way you can tell that the index is corrupt is when you do a find and the wrong records are returned, as in your case. Sometimes records that you know are in there get lost etc. A corrupt index is obviously not a common occurrence, but it does occasionally happen.