From: Chris Robinson 

Ellen K wrote:

> If you set the source of the form to the table, the form is
"bound to" the
> table.  This will always be the case if you create a form by means of a
wizard.
>

Ah right - I see what you mean.  Would it still be the case if you used a wizard
but set a query as the source?

> I think you would have to update the field on the bound form to the value of
> the textbox on the other form (again, if you needed a Long, your statement
> would be MyTextboxOnThisForm = CLng(Forms!OtherForm!OtherTextbox)), then save
> the record.
>
> But personally I never use bound forms for data entry.
>

I'll bear that in mind for future ref - thanks for the tip.

Chris :o)

>
> > From: Chris Robinson 
> > Hmm that sounds like fun :oP...  I figured the temporary table might not be
> > too fantastic but it's not a massive app and doesn;t need to be mega fast
or
> > scaled up at any point (wouldn't have written it in Access ;o) - but,
thanks
> > for the tips there - I'll take a look at that.  I did check the fields'
data
> > types and I couldn't change them (there were no options in the format tab
of
> > Access to change this.  I'll have another look now you mentioned that
though
> > :o) - Thanks.
> > Oh yeh..... what's a bound form?
> > Chris.
> > "Ellen K." wrote:
> >> The error message indicates you have a type conversion
failure, i.e. the
> >> data type of the "employee" field on the other form
doesn't match the
> >> data type of the field in the table.
> >>
> >> You could try forcing the textbox on the other form to use the same
> >> datatype as the field in your table, or use code to explicitly convert
> >> the datatype before you post it, e.g. maybe in your table you
defined it
> >> as a long, but the way you populate the textbox on the other form makes
> >> a string, then you would convert it back by
> >> CLng(Forms!OtherForm!MyTextbox).   However the second solution won't
> >> work if you're using a bound form to populate the table.   (Bound forms
> >> are evil.)
> >>
> >> On Thu, 19 Jun 2003 10:44:50 +0100, Chris Robinson
> >>  wrote in message
> >> :
> >>
> >> >Here's on for all you Access Guru's ;o)
> >> >
> >> >I have a database (Access 2000) and I'm simply trying to
add data to a
> >> >table.  I have a form set up that allows me to add a new
record to a
> >> >table.  I can open this form, type away, click
"save" (a button I'd set
> >> >up to save the record) and voila - a new record appears
in my table.
> >> >
> >> >This all works fine when I manually type in the information, but
> >> >problems start to appear when I set the "default
vaule" for a field
> >> >(e.g. my "employee" field on my add record
form) to contain a value from
> >> >another form.  The value appears in the employee field without any
> >> >problems but when I click "save" and then check
my table - nothing's
> >> >there!  The record hasn't been added.  If I go back to
the form and type
> >> >over the value in the employee field with the exact same
value, it adds
> >> >the record - strange?
> >> >
> >> >Any ideas?
> >> >
> >> >I've also tried to add the record using an append query
which grabs the
> >> >employee field from another form but that doesn't add the
record either
> >> >- but it gives an error (whereas the form doesn't) - hope
it's ok to
> >> >post this in here rather than binaries - it's only small:
> >> >
> >> >[Image]
> >> >
> >> >I can't find much of use in Access help about this one
(clicking YES
> >> >does nothing by the way).
> >> >
> >> >Help! :oP
> >> >
> >> >Chris.

--- BBBS/NT v4.01 Flag-4