Column Identified is not known

[t16turbo]

HI,

I have changed a part of my ObtainSelectStatemet and when I now run the report I get a basic error:

DB Error 15: Column Identified is not known to this statement.

when I choose to debug it displays "No User Source"


the report can go through one of 3 ObtainSelectStatement paths, so I have forced it to go down the route of one that I have not changed and it now displays this error no matter what happens.

Can anyone suggest where to look?

thanks in advance

 

[gdwood]

That error can be a pain, but take a look and make sure that you have bound the columns that you need, that they are the right type, and that you have them all defined in the DataRow. If that fails you'll have to check your connection to the source and make sure that is configured properly. When you have multi-selects that can take a bit.

One last thing that can throw this error is if your select sorts the data for you, ensure that the report section sorting is set to PreSorted. The Automatic sorting option can cause issues with the buffer and can throw this error sometimes.

 

[t16turbo]

when you say 'bound the columns' what do you mean?
sorry - it must be a stupid question, but just want to make sure i'm not making a fundamental mistake.


thanks for the tips, i'll check them all and hopefully fix it.

thats if I can open my report again.
I posted another thread about this, but when I save my report, it saves it with no size - so I cant open it again...

 

[gdwood]

you don't use a source control tool like sourcesafe? I'd suggest it, just save RODs in there. As you know working with Actuate can lead to lost code. Try deleting all the files except the ROD and open again.

by bound the columns I mean the method:

Sub BindDataRow( cursor As AcDBCursor )

Now this depends on how you do your reports. What we do is create a cursor for each report so that we only pull the columns that we need and then can use the cursor for certain functions and manipulation.

So for a datastream, we have a select statement (we put this in the start method but you decide where is works best)

Then we use the BindDataRow method to bind all the columns to the cursor. Then we create the datarow object and add all the variables that we need on that row. And if these are not all in sync you can get that No user source error.

Let me know if this helps or confuses you even more.

 

[t16turbo]

We dont use any source control tool, but I think I am going to!
I'll try deleting other files (I guess you mean the roi, and rox etc?


I've not ued the BindDataRow method (i'm quite new to Actuate) bu maybe i'll look into it!!
thank you very much for your help.

 

[gdwood]

Yes, the bas file, roi, rox, rov, sometimes those 'hold on' and cause issues.

Well, I'm not going to say that you shoudl do what we do in regards to report design, but this works well for us and we have some complex design that tap Oracle and db2. We also use a ton of libaries for common components, which I would suggest to do. The report layout and components (datastreams, labels, text boxes) are all predefined for every report to make them standardized and quicker to develop.