Linking Access(urgent)

Dear all
I've a problem when I make a command button in Access's Form which open form or report the message that "error encountered with OLE ActiveX?"
Can any body help me to fix this ?
PLZ Help me urgentCould you give the exact error message, # etc. That would help.

servers "Client unable to establish connection"

We have several linked SQL servers running both SQL 7 (sp4) and SQL 2000 (sp3). Recently, when we run the following command from SQL 7 query analyzer to a SQL 2000 database, select * from remoteserver.database.dbo.tablename, we get this message:

[OLE/DB provider returned message: Client unable to establish connection]
[DBNMPNTW]ConnectionOpen (CreateFile()).

The databases are linked with specific remote login and password. The same command works the opposite direction, in other words from the SQL 2000 database to SQL 7 database. This was working last week but all of a sudden stopped. Of course, no one admits to changing anything on either of the servers. The SQL 2000 is on Windows 2003 server.

Thanks.

LccTom,

It is possible that some of the recent w2k3 patches disabled the file sharing and remote network connectivity on your w2k3 machine. Can you try if you can remote access to the w2k3 machine, such as file sharing? If you can't, you need to enable the file sharing because the namepipe provider[DBNMPNTW] depends on it.

Also, if you want TCP connection, you need to make firewall exception for the SQL tcp listening port, default to 1433 for a default instance.

|||We have no OS service packs installed but for some reason, it started working again Wednesday morning. Thanks for the reply and I'll make sure to look at the file sharing if it happens again. I reported it to my network people also.

server to VFPOLEDB working in 2000 but not in 2005?

I have run the following command and opened a working linked server in SQL Server 2000 but it fails for 2005.

sp_addlinkedserver 'AZ','','VFPOLEDB','c:\comp01\company.dbc'

To test, I run: select * from openquery(AZ, 'select * from contact') and I ge

Msg 7399, Level 16, State 1, Line 2

The OLE DB provider "VFPOLEDB" for linked server "AZ" reported an error. Access denied.

Msg 7350, Level 16, State 2, Line 2

Cannot get the column information from OLE DB provider "VFPOLEDB" for linked server "AZ".

The specs on the working machine: WinXP Pro, SQL Server 2000 Developer's Edition, SP4, latest VFPOLEDB from MS site.

The specs on the non-working machine: Windows Server 2003 (std), SQL Server 2005 Developer Edition SP4, latest VFPOLEDB from MS site.

Other things I have done and/or noticed:

- in the install notes, it says something about security through component services, MSDTC, having to check everything. Did that.

- if I don't use a SQL command from query analyzer and try to add the linked server by right clicking on Server Objects\Linked Servers, it demands a Product Name. Null (and ' ') is not a valid entry.

Looking for help on this.

Doug

Think I'm closer. Turns out that MDAC has not recognized VFPOLEDB despite having downloading and installed it on Windows Server 2003. I have now tried regsvr32 and it says it's registered but still not listed in MDAC (used the component checker). Thoughts?
|||Sorry, I don't have any suggestions for you. I just thought I'd sympathize because I am running into the same problem with MSDAORA instead of VFPOLEDB. I'd be interested to hear what progress you end up making.

server to VFPOLEDB working in 2000 but not in 2005?

I have run the following command and opened a working linked server in SQL Server 2000 but it fails for 2005.

sp_addlinkedserver 'AZ','','VFPOLEDB','c:\comp01\company.dbc'

To test, I run: select * from openquery(AZ, 'select * from contact') and I ge

Msg 7399, Level 16, State 1, Line 2

The OLE DB provider "VFPOLEDB" for linked server "AZ" reported an error. Access denied.

Msg 7350, Level 16, State 2, Line 2

Cannot get the column information from OLE DB provider "VFPOLEDB" for linked server "AZ".

The specs on the working machine: WinXP Pro, SQL Server 2000 Developer's Edition, SP4, latest VFPOLEDB from MS site.

The specs on the non-working machine: Windows Server 2003 (std), SQL Server 2005 Developer Edition SP4, latest VFPOLEDB from MS site.

Other things I have done and/or noticed:

- in the install notes, it says something about security through component services, MSDTC, having to check everything. Did that.

- if I don't use a SQL command from query analyzer and try to add the linked server by right clicking on Server Objects\Linked Servers, it demands a Product Name. Null (and ' ') is not a valid entry.

Looking for help on this.

Doug

Think I'm closer. Turns out that MDAC has not recognized VFPOLEDB despite having downloading and installed it on Windows Server 2003. I have now tried regsvr32 and it says it's registered but still not listed in MDAC (used the component checker). Thoughts?
|||Sorry, I don't have any suggestions for you. I just thought I'd sympathize because I am running into the same problem with MSDAORA instead of VFPOLEDB. I'd be interested to hear what progress you end up making.

server to VFPOLEDB working in 2000 but not in 2005?

I have run the following command and opened a working linked server in SQL Server 2000 but it fails for 2005.

sp_addlinkedserver 'AZ','','VFPOLEDB','c:\comp01\company.dbc'

To test, I run: select * from openquery(AZ, 'select * from contact') and I ge

Msg 7399, Level 16, State 1, Line 2

The OLE DB provider "VFPOLEDB" for linked server "AZ" reported an error. Access denied.

Msg 7350, Level 16, State 2, Line 2

Cannot get the column information from OLE DB provider "VFPOLEDB" for linked server "AZ".

The specs on the working machine: WinXP Pro, SQL Server 2000 Developer's Edition, SP4, latest VFPOLEDB from MS site.

The specs on the non-working machine: Windows Server 2003 (std), SQL Server 2005 Developer Edition SP4, latest VFPOLEDB from MS site.

Other things I have done and/or noticed:

- in the install notes, it says something about security through component services, MSDTC, having to check everything. Did that.

- if I don't use a SQL command from query analyzer and try to add the linked server by right clicking on Server Objects\Linked Servers, it demands a Product Name. Null (and ' ') is not a valid entry.

Looking for help on this.

Doug

Think I'm closer. Turns out that MDAC has not recognized VFPOLEDB despite having downloading and installed it on Windows Server 2003. I have now tried regsvr32 and it says it's registered but still not listed in MDAC (used the component checker). Thoughts?
|||Sorry, I don't have any suggestions for you. I just thought I'd sympathize because I am running into the same problem with MSDAORA instead of VFPOLEDB. I'd be interested to hear what progress you end up making.