You may need to reindex the tables. Or, you may have a relation set to an index that no longer exists.
Check your data and environment for those issues to start with.
take a look at code/cursor objects in the data environment in the rpttable report. If they need an index on cursor1, you'll need to INDEX ... TAG .. after the SELECT, which would need SELECT .... INTO CURSOR cursor1 READWRITE beforehand.
Well, I can't say that by the code you gave, as I don't have insight into the report and it's data environment. I don't know how the tag should be named and which fields or expression is needed for the index definition.
SELECT Rpttable.id1, Rpttable.fname, Rpttable.lname, Rpttable.company,;
Rpttable.expiredate, Rpttable.idz, Rpttable.pubname, Rpttable.effgroup;
FROM rpttable;
INTO CURSOR cursor1 READWRITE
would be a beginning. Now you should tell me by the needs of the report, what INDEX ON ... TAG ... you need on cursor1.
Have you edited the report (MODIFY REPORT rpttable) and taken a look at it's data environment?
Olaf, our data environment includes one table which is the rpttable that you see contained in the SELECT statement. All of the fields of this table are selected as well. Cursor1 seems to error out indicating an index tag is needed. We don’t know where the index tag is needed. Thanks so much for all your help with this.
Who has done that Report? He should know, which index has to be created on cursor1. And if you get that error there has to be some code setting the order (SET ORDER TO <Tagname> or SET ORDER TO <Tagnumber>) or some property like Order has to be set to some value.
Check the properties of the Cursor-Object in the dataenvironment, choose the Data Tab and tell me what the 'Order' property is set to, also the Property 'Alias' and the Property 'Name' (which can be found on the Tabs 'All' or 'Others').
If the Order-Property is not set, look inside the code of the dataenvironment. The OpenTables-Method is a candidate for opening tables programmatically or setting orders, look for SET ORDER TO.
If you have a CursorObject named Cursor1 in the dataenvironment it's probably not a good idea to name a the Cursor you create by SQL-Select before calling REPORT FORM the same name. It's not illegal but can be very confusing. Maybe that index is indeed missing on rpttable, not on cursor1.
Fact is, the CursorObject of the database is not a Cursor, it's an object for a table,view or cursor, in this case for the table rpttable.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.