My Custom StoredProcedures are not returning TList<Entity>

Hello guys,

This seems to be weird issue but I cannot get my custom StoredProcedure to return collection I am still getting default DataReader.

I have tried nearly everything:

I prepared _tblAddress_GePagedTest SP and copyied all SQL code from existing generated (byCodeSmith 4.0) SP named dbo.tblAddress_GetPaged just for test - it is just selecting fields (all) from tblAddress table but for my generated code I am always getting default DataReader.

I tryed also to re-open CodeSmith to refresh schema but still without success.

Also noticed that custom stored procedures are not generated for my service layer is this feature available?

Does anybody experience this issues?

Thanks

Carl  

If you just did a "Cut and paste" from an auto generated proc you probably also included the last statement "Select @@ROWCOUNT".  If you did remove it!

For NT to be able to match your Select to your business entity automatically the business data must be the only returned dataset.

Your custom procs should be available in your service layer if they are picked up by the data layer.

HTH

swin

swin, thanks for advice.

But I tried that as well and my current custom sproc is nothing else just select [field1],... [fieldN] from TableName (but still getting DataReader generated on output)

Is there something hidden in option that I ommited, or is this is something like application CodeSmith generator error that cannot recognize clean business class somehow?

Thanks

Carl  

Do you have any User Defined Datatypes in your table? These will cause NetTiers to give a dataset insetad of a TList. You need to replace them with the native data type. You can do this with ALTER TABLE xxx ALTER COLUMN xxx in SQL Server 2005.

We now have 2 databases - one we use for generation that has no data (except Enum tables), only the relationships and indices we want to appear in code, custom sprocs and no UDTs. The other database is our normal database.

Carl,

Are you 100% sure all columns returned EXACTLY match the columns in the table.  This includes their order, type, size etc.

For example I had a csp which I needed to just drop an image column - to get NT to pick this null column up and give me a TList had had to cast a null to image.

HTH

swin

Thanks DavidB,

It was EXACTLY that problem I had. I have been using UDT and this was causing that problem. Now it's resolved and finally it's working.

Thanks guys!!!

Cheers 

Can you confirm that Custom Stored Procedures only return a structured recordset <list> if they exactly represent an underlying table?