How many tables per VIEW can a webservice reasonaable handle?

[Wolfgang Orth]

Hello Bruce,

a quick question as a follow-up to your Webinar.

My datasets are somewhat complex, on some FORMs they span across 20 related tables.

Is it possible to build a webservice for such monsters?

Am I right with my assumption that I do a series of LOOPs with  SET / NEXT or ACCESS:table.Fetch() through all related child-/grandchild/and-so-on-tables to read all the required records on the server-side, then send back my dataset to the client?

Thanks in advance, bye
Wolfgang

[Bruce]

Hi Wolfgang,

I recommend you read up a bit on the VIEW structure. Perhaps experiment a bit with how they work etc. there were some excellent articles on them on ClarionMag as well.

In short, they are very powerful and probably do all the work for you. I'm not aware of any limitation when it comes to the number of levels, or number of tables.

Cheers
Bruce

[osquiabro]

tps or SQL? if SQL create a view in server side and import in your dct like a single table.

if tps is recommended move to SQL