[thelist] ms access website solution?

[Robert Teasdale]

Hi Ken,

Thanks for your reply.
--------------
KS
David was talking about not being able to update a database. How is this the
same as not being able to connect to a database?
--------------------

I cannot update 'detail' on my database.
Here I want to add more fields to the Form and the .mdb created . This was
all generated by FP Wizard but to do this it has to establish the
'connection string' as step 1. The error message received is because it now
does not recognise my connection string?
-------------
Error Message:
Unable to connect to database from the web server using the connection
string,
DRIVER={Microsoft Access Driver(*.mdb)};DBQ=URL=_private/fpdb/supplier.mdb
-----------------
My only additions to software recently downloaded are;
1. Downloaded the MDAC 2.8 update including the latest ODBC Driver.
2. Windows XP Office Pro SP3
3. MS Jet 4.0.8618.0 update.
These were listed by MS as recommended updates.!

Obviously not making many changes to my databases on the web, so at a loss
to know which one may or may not have affected my 'connection string'.

I will as you suggest try FP Group and see if anyone else has recently
noticed this issue.

Thank you

Best Regards
Rob

----- Original Message ----- 
From: "Ken Schaefer" <ken at adOpenStatic.com>
To: <thelist at lists.evolt.org>
Sent: Monday, May 03, 2004 1:53 AM
Subject: Re: [thelist] ms access website solution?


> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> From: "Robert Teasdale" <robert.teasdale33 at ntlworld.com>
> Subject: Re: [thelist] ms access website solution?
>
>
> : I think I may also be experiencing this loss of database
> : connection since MDAC recommended upgrade.
> :
> : MDAC_TYP
> : Win32 Cabinet Self Extractor
> :
> : I appear to have lost and cannot create new database connections using
> : Office XP Pro with FP2002.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> >
> mdac_typ.exe is the name for all MDAC updates. I think you'd need to be
able
> to tell us what MDAC you have before, and what you have now. Be aware also
> that recent MDACs do not update the Jet ODBC drivers or OLEDB Providers at
> all.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> : Error Message:
> : ---------------------------
> : Unable to connect to database from the web server using the connection
> : string,
> : DRIVER={Microsoft Access
> Driver(*.mdb)}-;DBQ=URL=_private/fpdb/supplier.mdb
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> That connection string appears to have a syntax error in it - there's a
"-"
> character just before the first ";". I do not think that's legal.
>
> Also, as mentioned, consider using the Jet OLEDB Provider:
>
> Provider="Microsoft.Jet.OLEDB.4.0;Data Source=" &
> Server.Mappath("_private/fpdb/supplier.mdb") & ";"
>
> Otherwise, if you are having Frontpage generate these connection strings,
I
> suggest you ask in an FP group.
>
> Cheers
> Ken
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> : The following error message comes from the database driver software.It
may
> : appear in a 'different language' depending on how the driver is
> configured.
> :
> : The specified procedure could not be found (ADODB.Connection)
> : Source ADO
> : Number -2147024769(0x80070107f)
> : ---------------------------
> : Do you know what this error message means?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> You are trying to execute a parametised query, but the query can not be
> found in the database. Without source code, it is impossible for me to
> debug...
>
> Cheers
> Ken
>
> -- 
> * * Please support the community that supports you.  * *
> http://evolt.org/help_support_evolt/
>
> For unsubscribe and other options, including the Tip Harvester
> and archives of thelist go to: http://lists.evolt.org
> Workers of the Web, evolt !
>