jwcolby
jwcolby at colbyconsulting.com
Wed Mar 16 14:36:09 CDT 2011
This seems to be a known issue without a resolution. http://www.utteraccess.com/wiki/index.php/Using_ADO It was occurring specifically when I was trying to use the subform linking. It really appears that when any form is bound to an ADO recordset there are a host of issues with the RecordsetClone (which is DAO) and that perhaps recordsetclone is used internally by DOA to support the form. John W. Colby www.ColbyConsulting.com On 3/16/2011 2:04 PM, Heenan, Lambert wrote: > http://support.microsoft.com/kb/300699 says "These errors occur when the database cannot be found because of a data source that is not valid in the ConnectionString for the page, or when the UseRemoteProvider property is not configured properly" > > http://xlinesoft.com/asprunnerpro/faq.htm#initialized says "This error can happen for a number of reasons. Usually it happens due to server components conflict. You can try one of the following things to resolve this problem: > > Restart IIS > > Restart computer > > Install or reinstall Microsoft Jet 4.0 Service Pack 6 (SP6) > > Reinstall Microsoft Data Access Components (MDAC)" > > Lambert > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby > Sent: Wednesday, March 16, 2011 1:04 PM > To: Access Developers discussion and problem solving > Subject: [AccessD] subform bound to ado recordset throws error > > "Data provider could not be initialized". > > Has anyone solved this? I see a ton of "me too" responses out on the internet but so far no "this is why and this is how to fix it. > > -- > John W. Colby > www.ColbyConsulting.com > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >