trying to use DAP for simple data entry over network

I am designing a mortgage aplication form that will be shared across a network.

I want to create a data access page that the users can use for data entry.

I had to create 3 tables for all the feilds. I have linked the tables
primary keys together using a one to one relationship. They have refrential
integrity and cascade update and delete.

I started to create a data access page and it has worked fine until it had
an error message : Too many feilds defined.

So as the page will get too big i split the mortgage application form in to
8 different data access pages and wanted to create a hyperlink at the end of
each page. I added a server filter CLRef=[CLRef] to carry the reference
number over to the next page and it works but it will only allow me to save
the data on the first page. On all other pages it is greyed out.

I tested it by creating a test page with feilds from all 3 tables and if i
open it directly it works fine but not when coming from the hyperlink.

Am i going about this wrong. It is a very simple data entry application form
for a mortagage company. Please can someone advise me. My brain feels
squished.

Thank you in advance

=?Utf-8?B?YWJ6enp6?= wrote in
:


Am i going about this wrong. It is a very simple data entry
application form for a mortgage company. Please can someone advise
me. My brain feels squished.



Probably, for a number reasons.

For a start, the consensus is that Data Access Pages were a bit of a
mistake and I don't think anyone is really developing on them any more.
If you want www access to a database, then ASP and a normal ADODB
connection is probably the way to go.

Secondly, I don't know how many fields count as too many (is it 255?) but
if you have enough to split into EIGHT forms, then it's no longer a "very
simple data entry" form. You could probably look a bit harder at the
processes and data structure, although clearly I don't have any idea of
what you are doing.

Thirdly (probably related to numb 2 above) is that three tables linked
one-to-one is hardly ever a good idea, and suggests that some Major
Redesign Work would be a good idea.

Sorry to be vague, but you have not given much detail to work on!

All the best


Tim F