ad hoc group errors

[pjames95003]

Hi,

We are using 7.2.2 Network. I have a user who is creating ad hoc groups for some marketing lists. The user has an ad hoc group with 11,000 contact records in it. When the user tried to export to Excel, he received the "Either BOF or EOF is True, or current record has been deleted" message. Using RJ's guidance to another user on another thread, I found the group members from the ADHOCGROUP table and ran query for them through query analyzer without any problem (Select * from Contact in...) and based on the SLX KB (457372), I have

1. confirmed that all date values are valid.
2. confirmed that none of the id columns have blank or null values.
3. Run Security.Sec Rights Records with invalid Sec Codes (Delete) within the Integrity checker. (zero records returned)
4. Looked at other data in the records for obvious issues.

The issue is not actually with the export; it is with returning the group result set. If I scroll through the records in the the form view, depending upon which column I have sorted on, I get to either record 98 or 99 or 299 before the error message pops. When it does, I am usually displayed record 11,000 (the last record) and if in the form view, I see "-1 of 11,000".

Is there some SQL Express or SLX limitation on the number of members in a "select from in " statement? Because the error pops at different record numbers, it does seem like a data issue, but I can't see it. Also, I did notice that the group contains about 200 duplicate records where the duplicate contactid appears anywhere from 2 to 4 times in the group. Also, when I clear the error, it appears again and again and again... not sure if that is because SLX cannot recover or because as soon as it recovers, it hits another exception.

I also looked at the SQL using SLXProfiler, and ran that through Query Analyzer and it showed nothing odd that I could find although it does use a calculated field (Last Name + First Name), but I couldn't find anything that said that would be a problem. (SQL Below)

Any thoughts? Thanks

Patrick


SELECT A1.CONTACTID, (isNull(A1.LastName,'') + ', ' + isNull(A1.FirstName,'')) NAMELF2, A1.ACCOUNT, A1.EMAIL,
A1.ACCOUNTMANAGERID, (isNull(A1.LastName,'') + ', ' + isNull(A1.FirstName,'')) NAMELF6, A1.SECCODEID SLXSECCODEID7
FROM sysdba.CONTACT A1
INNER JOIN sysdba.SECRIGHTS S_AA ON (S_AA.ACCESSID = 'U6UJ9A00000O' AND A1.SECCODEID = S_AA.SECCODEID )
INNER JOIN sysdba.ADHOCGROUP A2 ON (A1.CONTACTID=A2.ENTITYID)
WHERE A2.GROUPID = 'p0TN0A9000CT' ORDER BY SLXSECCODEID7

[apfingstl]

Hi,

I think there is a bug with export to excel and specific amount of records.

What is if you have one recorde more in your group. Does it work then?

Alexander

[pjames95003]

Thanks for the reply Alexander.  The problem appears to be before the export. I can't even scroll through the records without the error. Still, I added one and then two more contacts to the group and still no change.  It seems to be hitting a limit of some sort. By default, the group is ordered by contact last name. In the list view, I can scroll 7 pages or to 299 records. After that, if I use my down arrows to try to go to record 300, nothing happens. It is as if only 299 records were returned.   So I added a few more contacts that appear within the top 300 records and still I can get to exactly the same record count, 299. I'm going to try a new ad hoc group with over 300 records to see if it happens on that group as well.

Patrick

[apfingstl]

Hi Patrick,

AS I said, I only know something with the export and a specific number or records in a group.

Have not heard about the scroll thing.

Sorry!

Have you tried it from different PCs to make sure that it is not realted to the installation of the client?

Alexander

[pjames95003]

Hi,

Yes, it has been tested on 3 different PC's, two different user accounts (both Windows and SLX). Same result. I created a new ad hoc with about 2000 records and there is no problem at all. I also added the same records into my new ad hoc group that would have been the next two screens of records in the original ad hoc group to see if it was just a single record on the next displayed screen that was causing a problem, but it still worked fine bringing back all records.