Best option would be to put addresses in their own table that you then link to each student by an address ID. Then you can get a duplicate free list of addresses from a layout based on the address table rather than the student table.
Otherwise, you'd be looking at a portal that filters out duplicates, an ExecuteSQL field that lists all addresses with Select Distinct used to filter out duplicates, a looping script that uses GetNthRecord to check for and omit duplicates or importing this data into a temp table where a "unique values, validate always" validation option filters out the duplicate during the import.
Thanks for your advise Phil,
I will figure this out, but if I look at the structure of the database, I think importing the data into a temp table is the most logical one (in this case).
Thanks again for your time Phil,
Sorry for getting back on this issue and use more of your time.
I used the import function, works all fine. But you made me curious about what you wrote; “an ExecuteSQL field that lists all addresses with Select Distinct used to filter out duplicates”
I thought that de “Select Distinct” only counts the unique values. So, I was wandering how to use this as a filter.
If you put DISTINCT inside the parameters of the count function, it's a count of unique values, but if you set up your query as:
SELECT DISTINCT a.field.....
you will be pulling up a record set of unique values--at least that's how I recall doing this previously....
O.K. Thanks for your explanation Phil,
That is helpful. I don't directly need it at this time, but it is good to learn these things for future use.
Thanks again Phil.