T
Ted
woops, i just reminded myself that the Lastedited field remains to be solved
for (needed to have the system autogenerate the DAteTime....
for (needed to have the system autogenerate the DAteTime....
Dirk Goldgar said:Ted said:here's the contents of the immediate window's:
INSERT INTO [DaysView] ([Last Name], [First Name], [MI],[MR_Number],
[IRB Number], [RecordNumber], [Updated_By]) SELECT "Adams" AS LN,
"Mary" AS FN, "--" AS MI, 1234567 AS MR, "04-04-083" AS IRB, 10 AS
VIS, "albertn" As UPD;
because of the sensitive personal nature of the information that
would be given here, i have had to alter the identifying information
(after carefully checking the material actually given in it for
accuracy); suffice it to say, the values for last/first/mi/mr which
are shown comport with their original's in appearance)
The statement looks fine, but I see from your next sentence why it was
failing.
lastly, you are right, both those fields you cited should be defined
as text fields in the underlying DaysView table, HOWEVER i found that
the Updated_By field had been changed inadvertantly to number field
Oops.
--- which i corrected to be Text.
the code ran w/o the data mismatch error!
Hurrah! It's fixed!
BUT following the focus
lines another message emerge ....
Object doesn't support property or method
following this line in the code below:
Me!DaysView!VisitType.SetFocus
I would guess that there is no control on the DaysView subform that is
actually named "VisitType". Check the name. "VisitType" may be the
name of the field the control is bound to, but not the name of the
control.
--
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)