After publishing my .asp page that utilizes a simple 2 field query with 10
records that works fine in Access, the results when calling the page in the
browser (using IIS and XP Pro), the first field in the search results table
returns:

"Microsoft VBScript runtime error '800a000d'

Type mismatch: 'FP_FieldVal'

/cemetery/test.asp, line 123"

Returning to FP to explore, when highlighting the field name within the
database results table, I get the following database connection error:

"Server error: Unable to retrieve the list of record sources from a database
using the connection string:
DRIVER={Microsoft Access Driver (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
The following error message comes from the database driver software; it may
appear in a different language depending on how the driver is configured.
Source: ADO
Number: -2146824584 (0x800a0e78)"

Can anybody give me a clue what this is about and how to fix it? Thanks.
--
Tom

See if the following KB article helps:
http://support.microsoft.com/default...b;en-us;243331

It may solve both problems actually but it's a good place to start as errant
issues with a conenction string can lead to very odd ADO and ASP behavior.

Hope this helps,
Mark Fitzpatrick
Microsoft MVP - FrontPage

"T. Utley" <(E-Mail Removed)> wrote in message
news:58F6A1EE-2DE1-4A44-A855-(E-Mail Removed)...
> After publishing my .asp page that utilizes a simple 2 field query with 10
> records that works fine in Access, the results when calling the page in
> the
> browser (using IIS and XP Pro), the first field in the search results
> table
> returns:
>
> "Microsoft VBScript runtime error '800a000d'
>
> Type mismatch: 'FP_FieldVal'
>
> /cemetery/test.asp, line 123"
>
> Returning to FP to explore, when highlighting the field name within the
> database results table, I get the following database connection error:
>
> "Server error: Unable to retrieve the list of record sources from a
> database
> using the connection string:
> DRIVER={Microsoft Access Driver
> (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
> The following error message comes from the database driver software; it
> may
> appear in a different language depending on how the driver is configured.
> Source: ADO
> Number: -2146824584 (0x800a0e78)"
>
> Can anybody give me a clue what this is about and how to fix it? Thanks.
> --
> Tom

Thanks Mark.

I read the URL you referenced, and while my inititial error message indeed
matches the subject article, both recommended solutions dealt with either WIN
2000 or NT neither of which I'm using. However, if the root of my problem
is, in fact, due to temp file access depending on whether I'm authoring or
browsing, then I'm thinking that this must be a very common issue that would
be encountered by virtually anyone who is using IIS on their local machine to
test their FP ASP pages prior to "going live". So, I'm still stuck. Any
suggestions?
--
Tom


"Mark Fitzpatrick" wrote:

> See if the following KB article helps:
> http://support.microsoft.com/default...b;en-us;243331
>
> It may solve both problems actually but it's a good place to start as errant
> issues with a conenction string can lead to very odd ADO and ASP behavior.
>
> Hope this helps,
> Mark Fitzpatrick
> Microsoft MVP - FrontPage
>
> "T. Utley" <(E-Mail Removed)> wrote in message
> news:58F6A1EE-2DE1-4A44-A855-(E-Mail Removed)...
> > After publishing my .asp page that utilizes a simple 2 field query with 10
> > records that works fine in Access, the results when calling the page in
> > the
> > browser (using IIS and XP Pro), the first field in the search results
> > table
> > returns:
> >
> > "Microsoft VBScript runtime error '800a000d'
> >
> > Type mismatch: 'FP_FieldVal'
> >
> > /cemetery/test.asp, line 123"
> >
> > Returning to FP to explore, when highlighting the field name within the
> > database results table, I get the following database connection error:
> >
> > "Server error: Unable to retrieve the list of record sources from a
> > database
> > using the connection string:
> > DRIVER={Microsoft Access Driver
> > (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
> > The following error message comes from the database driver software; it
> > may
> > appear in a different language depending on how the driver is configured.
> > Source: ADO
> > Number: -2146824584 (0x800a0e78)"
> >
> > Can anybody give me a clue what this is about and how to fix it? Thanks.
> > --
> > Tom
>
>
>

The issue w/ temp/tmp is the same on all version of Windows (XP Pro and 2003)
- but since you are getting it on a hosted server (not your localhost) it may be a permissions problem by your host

But often a Type mismatch indicates your data in the query does not match the field type you are using

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


"T. Utley" <(E-Mail Removed)> wrote in message news:5FBC57E5-AB00-4CB3-9070-(E-Mail Removed)...
| Thanks Mark.
|
| I read the URL you referenced, and while my inititial error message indeed
| matches the subject article, both recommended solutions dealt with either WIN
| 2000 or NT neither of which I'm using. However, if the root of my problem
| is, in fact, due to temp file access depending on whether I'm authoring or
| browsing, then I'm thinking that this must be a very common issue that would
| be encountered by virtually anyone who is using IIS on their local machine to
| test their FP ASP pages prior to "going live". So, I'm still stuck. Any
| suggestions?
| --
| Tom
|
|
| "Mark Fitzpatrick" wrote:
|
| > See if the following KB article helps:
| > http://support.microsoft.com/default...b;en-us;243331
| >
| > It may solve both problems actually but it's a good place to start as errant
| > issues with a conenction string can lead to very odd ADO and ASP behavior.
| >
| > Hope this helps,
| > Mark Fitzpatrick
| > Microsoft MVP - FrontPage
| >
| > "T. Utley" <(E-Mail Removed)> wrote in message
| > news:58F6A1EE-2DE1-4A44-A855-(E-Mail Removed)...
| > > After publishing my .asp page that utilizes a simple 2 field query with 10
| > > records that works fine in Access, the results when calling the page in
| > > the
| > > browser (using IIS and XP Pro), the first field in the search results
| > > table
| > > returns:
| > >
| > > "Microsoft VBScript runtime error '800a000d'
| > >
| > > Type mismatch: 'FP_FieldVal'
| > >
| > > /cemetery/test.asp, line 123"
| > >
| > > Returning to FP to explore, when highlighting the field name within the
| > > database results table, I get the following database connection error:
| > >
| > > "Server error: Unable to retrieve the list of record sources from a
| > > database
| > > using the connection string:
| > > DRIVER={Microsoft Access Driver
| > > (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
| > > The following error message comes from the database driver software; it
| > > may
| > > appear in a different language depending on how the driver is configured.
| > > Source: ADO
| > > Number: -2146824584 (0x800a0e78)"
| > >
| > > Can anybody give me a clue what this is about and how to fix it? Thanks.
| > > --
| > > Tom
| >
| >
| >

Thanks for the input Stefan. I'm sorry I wasn't clear about my server. The
error is occuring on my localhost, so maybe permissions are the issue. I'm
using a query that was developed within Access, and I'm reasonably certain
their are no data type missmatches since the query runs just fine in Access.
Any suggestions on how to insure that my permissions are correct? Or any
other suggestions? Thanks
--
Tom


"Stefan B Rusynko" wrote:

> The issue w/ temp/tmp is the same on all version of Windows (XP Pro and 2003)
> - but since you are getting it on a hosted server (not your localhost) it may be a permissions problem by your host
>
> But often a Type mismatch indicates your data in the query does not match the field type you are using
>
> --
>
> _____________________________________________
> SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
> "Warning - Using the F1 Key will not break anything!" (-;
> To find the best Newsgroup for FrontPage support see:
> http://www.net-sites.com/sitebuilder/newsgroups.asp
> _____________________________________________
>
>
> "T. Utley" <(E-Mail Removed)> wrote in message news:5FBC57E5-AB00-4CB3-9070-(E-Mail Removed)...
> | Thanks Mark.
> |
> | I read the URL you referenced, and while my inititial error message indeed
> | matches the subject article, both recommended solutions dealt with either WIN
> | 2000 or NT neither of which I'm using. However, if the root of my problem
> | is, in fact, due to temp file access depending on whether I'm authoring or
> | browsing, then I'm thinking that this must be a very common issue that would
> | be encountered by virtually anyone who is using IIS on their local machine to
> | test their FP ASP pages prior to "going live". So, I'm still stuck. Any
> | suggestions?
> | --
> | Tom
> |
> |
> | "Mark Fitzpatrick" wrote:
> |
> | > See if the following KB article helps:
> | > http://support.microsoft.com/default...b;en-us;243331
> | >
> | > It may solve both problems actually but it's a good place to start as errant
> | > issues with a conenction string can lead to very odd ADO and ASP behavior.
> | >
> | > Hope this helps,
> | > Mark Fitzpatrick
> | > Microsoft MVP - FrontPage
> | >
> | > "T. Utley" <(E-Mail Removed)> wrote in message
> | > news:58F6A1EE-2DE1-4A44-A855-(E-Mail Removed)...
> | > > After publishing my .asp page that utilizes a simple 2 field query with 10
> | > > records that works fine in Access, the results when calling the page in
> | > > the
> | > > browser (using IIS and XP Pro), the first field in the search results
> | > > table
> | > > returns:
> | > >
> | > > "Microsoft VBScript runtime error '800a000d'
> | > >
> | > > Type mismatch: 'FP_FieldVal'
> | > >
> | > > /cemetery/test.asp, line 123"
> | > >
> | > > Returning to FP to explore, when highlighting the field name within the
> | > > database results table, I get the following database connection error:
> | > >
> | > > "Server error: Unable to retrieve the list of record sources from a
> | > > database
> | > > using the connection string:
> | > > DRIVER={Microsoft Access Driver
> | > > (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
> | > > The following error message comes from the database driver software; it
> | > > may
> | > > appear in a different language depending on how the driver is configured.
> | > > Source: ADO
> | > > Number: -2146824584 (0x800a0e78)"
> | > >
> | > > Can anybody give me a clue what this is about and how to fix it? Thanks.
> | > > --
> | > > Tom
> | >
> | >
> | >
>
>
>

Running in Access the type mismatches are "self handled" by Access
Running in ASP you need to be explicit on declaring variable types (dates vs #'s vs txt)

Test your variable types using
response.write TypeName(yourvariablename) & "<br>" 'Debug testing only



--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
_____________________________________________


"T. Utley" <(E-Mail Removed)> wrote in message news:C4DDCFDE-DCD4-42EA-9B5B-(E-Mail Removed)...
| Thanks for the input Stefan. I'm sorry I wasn't clear about my server. The
| error is occuring on my localhost, so maybe permissions are the issue. I'm
| using a query that was developed within Access, and I'm reasonably certain
| their are no data type missmatches since the query runs just fine in Access.
| Any suggestions on how to insure that my permissions are correct? Or any
| other suggestions? Thanks
| --
| Tom
|
|
| "Stefan B Rusynko" wrote:
|
| > The issue w/ temp/tmp is the same on all version of Windows (XP Pro and 2003)
| > - but since you are getting it on a hosted server (not your localhost) it may be a permissions problem by your host
| >
| > But often a Type mismatch indicates your data in the query does not match the field type you are using
| >
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| > http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| > "T. Utley" <(E-Mail Removed)> wrote in message news:5FBC57E5-AB00-4CB3-9070-(E-Mail Removed)...
| > | Thanks Mark.
| > |
| > | I read the URL you referenced, and while my inititial error message indeed
| > | matches the subject article, both recommended solutions dealt with either WIN
| > | 2000 or NT neither of which I'm using. However, if the root of my problem
| > | is, in fact, due to temp file access depending on whether I'm authoring or
| > | browsing, then I'm thinking that this must be a very common issue that would
| > | be encountered by virtually anyone who is using IIS on their local machine to
| > | test their FP ASP pages prior to "going live". So, I'm still stuck. Any
| > | suggestions?
| > | --
| > | Tom
| > |
| > |
| > | "Mark Fitzpatrick" wrote:
| > |
| > | > See if the following KB article helps:
| > | > http://support.microsoft.com/default...b;en-us;243331
| > | >
| > | > It may solve both problems actually but it's a good place to start as errant
| > | > issues with a conenction string can lead to very odd ADO and ASP behavior.
| > | >
| > | > Hope this helps,
| > | > Mark Fitzpatrick
| > | > Microsoft MVP - FrontPage
| > | >
| > | > "T. Utley" <(E-Mail Removed)> wrote in message
| > | > news:58F6A1EE-2DE1-4A44-A855-(E-Mail Removed)...
| > | > > After publishing my .asp page that utilizes a simple 2 field query with 10
| > | > > records that works fine in Access, the results when calling the page in
| > | > > the
| > | > > browser (using IIS and XP Pro), the first field in the search results
| > | > > table
| > | > > returns:
| > | > >
| > | > > "Microsoft VBScript runtime error '800a000d'
| > | > >
| > | > > Type mismatch: 'FP_FieldVal'
| > | > >
| > | > > /cemetery/test.asp, line 123"
| > | > >
| > | > > Returning to FP to explore, when highlighting the field name within the
| > | > > database results table, I get the following database connection error:
| > | > >
| > | > > "Server error: Unable to retrieve the list of record sources from a
| > | > > database
| > | > > using the connection string:
| > | > > DRIVER={Microsoft Access Driver
| > | > > (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
| > | > > The following error message comes from the database driver software; it
| > | > > may
| > | > > appear in a different language depending on how the driver is configured.
| > | > > Source: ADO
| > | > > Number: -2146824584 (0x800a0e78)"
| > | > >
| > | > > Can anybody give me a clue what this is about and how to fix it? Thanks.
| > | > > --
| > | > > Tom
| > | >
| > | >
| > | >
| >
| >
| >

Thanks Stefan. Unfortunately, I wasn't sure how to run the debug script you
suggested, but I poured over my database manually looking for any data type
missmatches without locating any. So, I created a FP ASP test page and began
experimenting with all sorts of simple database search results from many
different tables and all returned the same: Type mismatch: 'FP_FieldVal'
with only the code line # varying.

For example, to test I queried a 2 field table: (category ID-auto numbered)
and a (name field-text) same results. My database utilized no 'reserved"
words which I noted in the only other post I've noted on this subject.

I'm truly stumped here. Can you or anyone give me some direction? I'd
really appreciate the help.
--
Tom


"Stefan B Rusynko" wrote:

> Running in Access the type mismatches are "self handled" by Access
> Running in ASP you need to be explicit on declaring variable types (dates vs #'s vs txt)
>
> Test your variable types using
> response.write TypeName(yourvariablename) & "<br>" 'Debug testing only
>
>
>
> --
>
> _____________________________________________
> SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
> "Warning - Using the F1 Key will not break anything!" (-;
> To find the best Newsgroup for FrontPage support see:
> http://www.net-sites.com/sitebuilder/newsgroups.asp
> _____________________________________________
>
>
> "T. Utley" <(E-Mail Removed)> wrote in message news:C4DDCFDE-DCD4-42EA-9B5B-(E-Mail Removed)...
> | Thanks for the input Stefan. I'm sorry I wasn't clear about my server. The
> | error is occuring on my localhost, so maybe permissions are the issue. I'm
> | using a query that was developed within Access, and I'm reasonably certain
> | their are no data type missmatches since the query runs just fine in Access.
> | Any suggestions on how to insure that my permissions are correct? Or any
> | other suggestions? Thanks
> | --
> | Tom
> |
> |
> | "Stefan B Rusynko" wrote:
> |
> | > The issue w/ temp/tmp is the same on all version of Windows (XP Pro and 2003)
> | > - but since you are getting it on a hosted server (not your localhost) it may be a permissions problem by your host
> | >
> | > But often a Type mismatch indicates your data in the query does not match the field type you are using
> | >
> | > --
> | >
> | > _____________________________________________
> | > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
> | > "Warning - Using the F1 Key will not break anything!" (-;
> | > To find the best Newsgroup for FrontPage support see:
> | > http://www.net-sites.com/sitebuilder/newsgroups.asp
> | > _____________________________________________
> | >
> | >
> | > "T. Utley" <(E-Mail Removed)> wrote in message news:5FBC57E5-AB00-4CB3-9070-(E-Mail Removed)...
> | > | Thanks Mark.
> | > |
> | > | I read the URL you referenced, and while my inititial error message indeed
> | > | matches the subject article, both recommended solutions dealt with either WIN
> | > | 2000 or NT neither of which I'm using. However, if the root of my problem
> | > | is, in fact, due to temp file access depending on whether I'm authoring or
> | > | browsing, then I'm thinking that this must be a very common issue that would
> | > | be encountered by virtually anyone who is using IIS on their local machine to
> | > | test their FP ASP pages prior to "going live". So, I'm still stuck. Any
> | > | suggestions?
> | > | --
> | > | Tom
> | > |
> | > |
> | > | "Mark Fitzpatrick" wrote:
> | > |
> | > | > See if the following KB article helps:
> | > | > http://support.microsoft.com/default...b;en-us;243331
> | > | >
> | > | > It may solve both problems actually but it's a good place to start as errant
> | > | > issues with a conenction string can lead to very odd ADO and ASP behavior.
> | > | >
> | > | > Hope this helps,
> | > | > Mark Fitzpatrick
> | > | > Microsoft MVP - FrontPage
> | > | >
> | > | > "T. Utley" <(E-Mail Removed)> wrote in message
> | > | > news:58F6A1EE-2DE1-4A44-A855-(E-Mail Removed)...
> | > | > > After publishing my .asp page that utilizes a simple 2 field query with 10
> | > | > > records that works fine in Access, the results when calling the page in
> | > | > > the
> | > | > > browser (using IIS and XP Pro), the first field in the search results
> | > | > > table
> | > | > > returns:
> | > | > >
> | > | > > "Microsoft VBScript runtime error '800a000d'
> | > | > >
> | > | > > Type mismatch: 'FP_FieldVal'
> | > | > >
> | > | > > /cemetery/test.asp, line 123"
> | > | > >
> | > | > > Returning to FP to explore, when highlighting the field name within the
> | > | > > database results table, I get the following database connection error:
> | > | > >
> | > | > > "Server error: Unable to retrieve the list of record sources from a
> | > | > > database
> | > | > > using the connection string:
> | > | > > DRIVER={Microsoft Access Driver
> | > | > > (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
> | > | > > The following error message comes from the database driver software; it
> | > | > > may
> | > | > > appear in a different language depending on how the driver is configured.
> | > | > > Source: ADO
> | > | > > Number: -2146824584 (0x800a0e78)"
> | > | > >
> | > | > > Can anybody give me a clue what this is about and how to fix it? Thanks.
> | > | > > --
> | > | > > Tom
> | > | >
> | > | >
> | > | >
> | >
> | >
> | >
>
>
>

How are you querying the data category ID field as a number or text?

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

"T. Utley" <(E-Mail Removed)> wrote in message
news:6CB198A1-8FB4-4261-9394-(E-Mail Removed)...
> Thanks Stefan. Unfortunately, I wasn't sure how to run the debug script you
> suggested, but I poured over my database manually looking for any data type
> missmatches without locating any. So, I created a FP ASP test page and began
> experimenting with all sorts of simple database search results from many
> different tables and all returned the same: Type mismatch: 'FP_FieldVal'
> with only the code line # varying.
>
> For example, to test I queried a 2 field table: (category ID-auto numbered)
> and a (name field-text) same results. My database utilized no 'reserved"
> words which I noted in the only other post I've noted on this subject.
>
> I'm truly stumped here. Can you or anyone give me some direction? I'd
> really appreciate the help.
> --
> Tom
>
>
> "Stefan B Rusynko" wrote:
>
>> Running in Access the type mismatches are "self handled" by Access
>> Running in ASP you need to be explicit on declaring variable types (dates vs #'s vs txt)
>>
>> Test your variable types using
>> response.write TypeName(yourvariablename) & "<br>" 'Debug testing only
>>
>>
>>
>> --
>>
>> _____________________________________________
>> SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
>> "Warning - Using the F1 Key will not break anything!" (-;
>> To find the best Newsgroup for FrontPage support see:
>> http://www.net-sites.com/sitebuilder/newsgroups.asp
>> _____________________________________________
>>
>>
>> "T. Utley" <(E-Mail Removed)> wrote in message
>> news:C4DDCFDE-DCD4-42EA-9B5B-(E-Mail Removed)...
>> | Thanks for the input Stefan. I'm sorry I wasn't clear about my server. The
>> | error is occuring on my localhost, so maybe permissions are the issue. I'm
>> | using a query that was developed within Access, and I'm reasonably certain
>> | their are no data type missmatches since the query runs just fine in Access.
>> | Any suggestions on how to insure that my permissions are correct? Or any
>> | other suggestions? Thanks
>> | --
>> | Tom
>> |
>> |
>> | "Stefan B Rusynko" wrote:
>> |
>> | > The issue w/ temp/tmp is the same on all version of Windows (XP Pro and 2003)
>> | > - but since you are getting it on a hosted server (not your localhost) it may be a
>> permissions problem by your host
>> | >
>> | > But often a Type mismatch indicates your data in the query does not match the field type you
>> are using
>> | >
>> | > --
>> | >
>> | > _____________________________________________
>> | > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
>> | > "Warning - Using the F1 Key will not break anything!" (-;
>> | > To find the best Newsgroup for FrontPage support see:
>> | > http://www.net-sites.com/sitebuilder/newsgroups.asp
>> | > _____________________________________________
>> | >
>> | >
>> | > "T. Utley" <(E-Mail Removed)> wrote in message
>> news:5FBC57E5-AB00-4CB3-9070-(E-Mail Removed)...
>> | > | Thanks Mark.
>> | > |
>> | > | I read the URL you referenced, and while my inititial error message indeed
>> | > | matches the subject article, both recommended solutions dealt with either WIN
>> | > | 2000 or NT neither of which I'm using. However, if the root of my problem
>> | > | is, in fact, due to temp file access depending on whether I'm authoring or
>> | > | browsing, then I'm thinking that this must be a very common issue that would
>> | > | be encountered by virtually anyone who is using IIS on their local machine to
>> | > | test their FP ASP pages prior to "going live". So, I'm still stuck. Any
>> | > | suggestions?
>> | > | --
>> | > | Tom
>> | > |
>> | > |
>> | > | "Mark Fitzpatrick" wrote:
>> | > |
>> | > | > See if the following KB article helps:
>> | > | > http://support.microsoft.com/default...b;en-us;243331
>> | > | >
>> | > | > It may solve both problems actually but it's a good place to start as errant
>> | > | > issues with a conenction string can lead to very odd ADO and ASP behavior.
>> | > | >
>> | > | > Hope this helps,
>> | > | > Mark Fitzpatrick
>> | > | > Microsoft MVP - FrontPage
>> | > | >
>> | > | > "T. Utley" <(E-Mail Removed)> wrote in message
>> | > | > news:58F6A1EE-2DE1-4A44-A855-(E-Mail Removed)...
>> | > | > > After publishing my .asp page that utilizes a simple 2 field query with 10
>> | > | > > records that works fine in Access, the results when calling the page in
>> | > | > > the
>> | > | > > browser (using IIS and XP Pro), the first field in the search results
>> | > | > > table
>> | > | > > returns:
>> | > | > >
>> | > | > > "Microsoft VBScript runtime error '800a000d'
>> | > | > >
>> | > | > > Type mismatch: 'FP_FieldVal'
>> | > | > >
>> | > | > > /cemetery/test.asp, line 123"
>> | > | > >
>> | > | > > Returning to FP to explore, when highlighting the field name within the
>> | > | > > database results table, I get the following database connection error:
>> | > | > >
>> | > | > > "Server error: Unable to retrieve the list of record sources from a
>> | > | > > database
>> | > | > > using the connection string:
>> | > | > > DRIVER={Microsoft Access Driver
>> | > | > > (*.mdb)};DBQ=URL=fpdb/CemeteryRegistry.mdb.
>> | > | > > The following error message comes from the database driver software; it
>> | > | > > may
>> | > | > > appear in a different language depending on how the driver is configured.
>> | > | > > Source: ADO
>> | > | > > Number: -2146824584 (0x800a0e78)"
>> | > | > >
>> | > | > > Can anybody give me a clue what this is about and how to fix it? Thanks.
>> | > | > > --
>> | > | > > Tom
>> | > | >
>> | > | >
>> | > | >
>> | >
>> | >
>> | >
>>
>>
>>