Info on this:

just run the grmGetRepositoryObjects stored procedure on my repository with 646 items inside with the following parameters:

EXEC @return_value = [dbo].[grmGetRepositoryObjects]
@ModuleID = 610,
@sFilter = N'',
@sSort = N'',
@Approved = 1,
@CategoryId = -1,
@Attributes = N'',
@RowCount = 2000

It runs like a charm and returns in about 1 sec. As far as I could see from the code, this is the initial call to the provider to get the first result set. So why the hack does it take 30-40 seconds when called from the module. There must be a lot more than only this to fill the module with data. The question is - what is really necessary here and what is just overhead.

will investigate further

Regards
Thomas

It is a pity i am not a coder, but hope Steve Fabian our Repository Guru will give us an insight at some stage