There are other ways to get that unique count.
ExecuteSQL, for example might be able to provide your unique count, to name one option. There's a way to use, of all things, a value list for counting unique values and sometimes it makes sense to set up a SSN table where only unique values are permitted and then you can count the records in that table instead of your current. You might also sort on SSN, get your count into a variable or global field and then sort to get what you need for your report, using the global variable or field to display the unique count.
Much depends on whether you are counting unique values found in your entire table or just a found set.
Which do you need?
Thank you for the info, the variable may be the way I may go.
Sorry forgot to mention this is based on a found set.
I added a variable to the script and worked perfectly! Simple addition fixed the problem ive been contending with for a long while, would never have thought of it without your help. Thank you again
Adding the variable also fixed the problem of the results for the SubSummary not showing up until the screen was active... even refreshing didn't work but adding variable somehow fixed that. Not really sure why but also not going to complain.
Okay, one last question... Is there a way to export the results of the Variable?
Yes, copy it to a field and then you can export it like any other data. You might use a field with global storage for this purpose.
And again a lifesaver. Think I can finally put this project to bed! Thank you again for all your help!