Good morning Bill,
I get this error message when trying to re-register the DLL. "The module C:\program files(x86)\Firebird\firebird_1_5\bin\fbclient.dll was loaded but the entry-point DLLRegisterServer was not found. Make sure that "C:\program files(x86)\Firebird\firebird_1_5\bin\fbclient.dll is a valid dll or OCX file and then try again."
I've searched Google on this error but haven't found anything yet that made sense or would fix the problem. I'll keep working on it but would appreciate any other ideas to fix this problem.
Thanks,
Doyce
--- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@...> wrote:
>
> Doyce
>
> The first thing I would try is to re-register the DLL. Then I would create a new DSN to see if that fixes it.
>
> Regards,
> Bill Mosca, Founder - MS_Access_Professionals
> http://www.thatlldoit.com
> Microsoft Office Access MVP
> https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
> My nothing-to-do-with-Access blog
> http://wrmosca.wordpress.com
>
>
>
> --- In MS_Access_Professionals@yahoogroups.com, "dnwinberry" <winberry.doyce@> wrote:
> >
> > Hello friends,
> >
> > I have Access 2007 linked to an application that uses a Firebird 1.5 database with an ODBC driver. This has worked well with Windows XP. Since I've upgraded my PC to Windows 7 64-bit, I can't get the Firebird ODBC driver to show up as a data source when I try to add an ODBC DSN. It does show up under the driver tab. Google searches have led me to believe this is a common problem, however I've not been able to find a workable solution. Can anyone help me link to these tables with Windows 7?
> >
> > Doyce
> >
>
Tidak ada komentar:
Posting Komentar