HREF I believe?

J

Jonathan

I have a problem (as a new coder to FP) I have an input form that posts to 1
access table that I want to break down into three separate input forms to
post to three different tables for speed and ease of reporting, however I am
stuck with the problem of taking the value of an input filed in form 1 to a
field in form 2 and then the same field value to pass to form 3 creating a
relation in the three separate tables - does this make sense?

I beleive I need to do somthing with HREF?

Any help would be greatly appreciated.

Tia


Jonathan
 
K

Kevin Spencer

I believe you're going to have to learn ASP.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
 
J

Jonathan

Hmmm, thanks for that - I know I need to learn ASP & I was hoping someone
could point me in the right direction - sorry to have been such as burden to
you!
 
K

Kevin Spencer

You're no burden, Jonathan. Let me explain what I meant. Your question
indicated that, while you have a pretty good idea of what you want to do,
you have virtually no knowledge of the tools (ASP and HTML in particular)
that you need to use to accomplish it. ASP is programming, at least
scripting, and there are no short cuts to learning how to program.

I could describe to you a house that I'd like to build without knowing
anything about building houses. I could tell you how many rooms it should
have, how big each room should be, where to put the kitchen, etc. But if I
had to build that house myself, I would have no other choice than to learn
carpentry.

FrontPage comes with some nice cookie-cutter tools that can create database
apps of the very simplest kind for you without your knowing much of anything
about it. That's all well and good. But if you want to customize your app,
your stepping outside the lines of what those tools can write for you, and
you have to write it yourself.

Now, some people have the mistaken impression that there are all kinds of
ready-made scripts out there to fit just about any requirement, but that
just aint so. Consider a chess set. It only has 32 pieces, but they can be
arranged in an almost infinite variety of configurations. Now consider a
programming language. It only has a few syntactical elements, but you can
create any kind of program with them.

So, the best advice I can give you is to roll up your sleeves and start
learning ASP!

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
 
M

Murray

Take Kevin's suggestion to heart.

In addition, your question is not too clear. Why do you need to put the
same value into three forms? Are these forms on different pages, or on the
same page?
 
J

Jonathan

Thanks Kevin, your right & I am trying to short cut (or should I say avoid)
the inevitable.

FP makes it very easy to get the basics in place (I have been using the DRW
wizard alot) but when it come to the more complicated stuff like what I am
trying to achive there is no wizard that will replace the hard coding I need
to do therefore I will get my ASP books out and try to learn from the
foundations up.

Thanks you
 
J

Jonathan

Thanks for your reply Murray,

My problem is I have an input form with 50 fields which at the moment is
submitting everything to 1 access table. However the input form could be
broken down into three separate parts:

1. customer contact details
2. current supplier details
3. Samples & Products left

In a database I would know that I link the tables through relationships
usually using the customer ID as the related field. I suppose my questions
should have been how do I do this in ASP?

Kevin is right though I should read up on ASP first.
 
M

Murray

You would submit the form to a process page that is coded to submit the
appropriate data to the appropriate table. There would be no need to try to
duplicate data across several forms.

I think Kevin has pointed you in the right direction.
 
Top