Re: Type Mismatch Error Message

Sorry...I was answering your questions in the order you asked them.

"Kevin Spencer" wrote:

> I'm so confused!!!
>
> > Using Text as SQL data type.
>
> This much I understand.
>
> > I didn't use the database wizard.
>
> I'll get back to that.
>
> > I created
> > one on a SQL server and named the columns identically to the FP form
> > fields.
>
> My head is beginning to hurt. One what? Where did "the FP form" come from?

I created a database on a SQL server manually and matched the column names
to mirror the fields in the FrontPage (FP) form.
>
> > I connected easily, and interestingly enough, can map some fields but not
> > all.
>
> You connected easily? I thought you "didn't use the database wizard?" The
> room begins to swim a little.

I was able to establish a network connection between the FrontPage form and
the SQL database. Remember, I didn't use the FrontPage (FP) form database
wizard to create the SQL database.
>
> > Data type in form is No Constraints.
>
> What "Data Type in form?" Again, where did this form come from? It really
> sounds suspiciously like some sort of reference to the "database wizard" you
> didn't use? Are you talking about form validation, or the mysterious
> "database wizard" that you didn't use?

If you open the validation window for any FrontPage (FP) form field you get
the option to change the data type to either "No Constraints, Text, Number,
or Integer."
>
> Referring back to your OP, I read:
>
> >> > When I attempt to map a FP2003 form field to a SQL database column I
> >> > receive
> >> > the following error message:
> >> >
> >> > "The type of field "additional_notes" does not match the type of column
> >> > "additional notes" in the database. Modify the field mapping or change
> >> > the
> >> > validation settings on the form field."
>
> Now, either you wrote ASP code that puts out error messages that look very
> suspiciously like something from the FrontPage database results wizard, or
> one of us is hallucinating. I'm hearing wizards all over the place! But you
> tell me they are not there!!

Psychotropic medication might help you! If you don't remember the 60s you
may be having acid flashbacks.

>
> Dwayne the bathtub! I'm dwowning!
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> ..Net Developer
> Expect the unaccepted.
>
> "Ed" <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:B22C9866-5617-423D-8FFD-1F2788037423@xxxxxxxxxxxxxxxx
> > Using Text as SQL data type. I didn't use the database wizard. I created
> > one on a SQL server and named the columns identically to the FP form
> > fields.
> > I connected easily, and interestingly enough, can map some fields but not
> > all. Data type in form is No Constraints.
> >
> > "Kevin Spencer" wrote:
> >
> >> What is the data type of the column in your database? What is the data
> >> type
> >> of the column in your Database Results Wizard?
> >>
> >> --
> >> HTH,
> >>
> >> Kevin Spencer
> >> Microsoft MVP
> >> ..Net Developer
> >> Everybody picks their nose,
> >> But some people are better at hiding it.
> >>
> >> "Ed" <Ed@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:8B1CBED2-F599-46B3-AE7F-ED44E0556CD1@xxxxxxxxxxxxxxxx
> >> > When I attempt to map a FP2003 form field to a SQL database column I
> >> > receive
> >> > the following error message:
> >> >
> >> > "The type of field "additional_notes" does not match the type of column
> >> > "additional notes" in the database. Modify the field mapping or change
> >> > the
> >> > validation settings on the form field." Additional notes is just one
> >> > of
> >> > many
> >> > fields for which I receive the error. Some are text, some numbers.
> >> > Originally I had all the fields set to No Constraints.
> >> >
> >> > I've tried changing the entry type from No Constraints to Text, as well
> >> > as
> >> > making the field data length required or not without success.
> >> >
> >> > Thanks in advance,
> >> >
> >> > Ed
> >>
> >>
> >>
>
>
>
.