Quick Portal and HTML From question

[Leb i Sol]

Hello enlightened people!

Could you shine some light on dark dillema:

I have 3 DBs related and in one of them I have a portal that is repeated/limited to 6 field entry. It works perfect!

how to replicate the same on AddRecord.html in the Form that is submitting the info?

- If I create indentical X number if fields on the AddRecord.html wouldn't that generate an error since all the fields would try to get stuffed into 1st?

.... If I am not clear: lets assume that I have a soccer team list that I am creating by entering data into the mentined portal in FM; now to replicate in HTML:

======AddRecord.html==========================

..............my team memebers:...............

____First Name____Last Name_______

1.[type here].......[type here]

2.[type here].......[type here]

...

...

..

10.[type here].......[type here]

11.[type here].......[type here]

......[ SUBMIT ]....[ RESET ].......

==========================================

would this then be entered in the portal or just the first field in the Portal would get populated and what happens if some form fields on HTML are left out empty?(maybe I just got 3 player names to enter right now)

thank you!!!!

[Garry Claridge]

With HTML it is very hard to submit multiple records (or portal rows). Usually one form is needed per record.

You could set-up this page so that you have an "Add Player" input at the bottom of the list. You can keep adding players to the list with a "Add/Submit" button.

Good Luck.

Garry

[Leb i Sol]

OK....that makes sense! Thanx garry!

-does portal limit(show 6 rows) to how many "additions" we can have?

thanx

[Garry Claridge]

No limits will exist for the number of Portal rows. However, you would be able to use some Javascript to set a limit.

All the best.

Garry

[Leb i Sol]

well...garry you just saved me some trial & error time!

Thank you sir!

[Anatoli]

FWIW

I've found that Portal serving is very slow with more than 50 portal records.

[Leb i Sol]

ouch..... |)

I guess it is time for some Major re-design of my DBs if I want them to "see the www"

thank you guys for the advice(s)!

[Anatoli]

Try it first with your maximum expected records + 100%.

Maybe you'll be more lucky

[Leb i Sol]

that is just it...I can not expect how many records I will have since they(come from LineItem.fp5) will grow contantly....so by the end of the year I might have 1000s of records.

My Question is then in that case how fast will portals respond?

eg. filter portal for a date range( A MUST for my porject)....returns 290 records

based on your 50+ experience...sounds like I would put a DSL user back to 28K modem experience whe nit comes to respond time!

I don't have to use portals but the decision time would be NOW rather than 1/2 year from now when user has to wait minutes before respond....

What do you say Anatoli?

[Anatoli]

As Garry suggested elsewhere, use backward relationship:

You will show the lines through flat file access (fast) "LineItem" and from backward relations the "Header".

Like you do when printing long Invoice across many pages.

HTH

[Leb i Sol]

never thought of that!

great I have enought ideas now to "get myslef in truble again"

Thank you guys!

p.s. I feel bad for Anatoli and Garry they have almost become my "personal consultants".....how can I repay...do you guys need any...."help"