Resumen Error al abrir un ADODB.Recordset

Mensaje enviado por pbajo@fbpba.org.ar

Esto lo encontré por ahi quizas te oriente.


Object does not support OLE Automation

This error can occur when:


An application has a reference to an object on a remote computer, and
is trying to pass a reference to local object as a parameter of a method of the remote object, and the Automation Manager is not installed properly on the local machine.


When a reference to a local object is passed to an application on another computer, the local computer becomes a Remote Automation server, and the Automation proxy must start the Automation Manager on the local machine. If the Automation Manager is on the machine, try starting it with the command line AUTMGR32 /REGSERVER to register it.
-2147220998 (&H800401FA) Wrong OS or OS version for application

The "Wrong OS version" error is caused by an incorrectly set InprocServer key. Each public class in a Visual Basic server has an entry in the CLSID section of the HKEY_CLASSES_ROOT registry key. Remote objects have their InprocServer (or InprocServer32) subkey set to the automation proxy. The automation proxy is Autprx32.dll for a 32-bit client on a 32-bit OS, Autprx16.dll for a 16-bit client on a 32-bit OS, and Autprx.dll for a 16-bit client on a 16-bit OS. This error can be raised when the InprocServer key is set to Autprx.dll on a 32-bit system. Because of a bug in the 16-bit Remote Automation Connection Manager on Windows 95, when an object is made
remote, the InprocServer key is set incorrectly in this manner. To fix this problem, do one of the following:

Manually edit the InprocServer key of each affected class so that it correctly points to Autprx16.dll.

-or-

Use the 16-bit client registration tool (Clireg16.exe) to remote your server instead of RacMan16. CliReg16 correctly detects what OS it is running under and will set the InprocServer key accurately. CliReg16 can be run from the command line with this syntax:

clireg16 server.vbr -t server.tlb.


-2146959355 (&H80080005)
Server Execution Failed
This error is caused by an incorrectly registered Autprx16.dll. Although Setup Wizard-generated setup programs will register Autprx16.dll completely, the Visual Basic 4.0 16-bit installation does not. To fix this problem, unregister and reregister Autprx16.dll with Regsvr.exe (or Regsvr16.exe).

Other Errors
Many errors encountered while working with Remote OLE Automation are characterized by a decimal error number that is both negative and longer than a usual error number. Errors that fit this description are most commonly OLE errors that are not mapped to a specific Visual Basic error.
The corresponding text for an error number like this can be found by searching for the hexadecimal equivalent of the number in the winerror.h header file that is included with Visual C++ and the Windows SDK.

The Unregister and Reregister Method of Cleaning the Registry Generally you can clean the registry entries for a specific server by unregistering and reregistering the relevant program. However, the method used to perform these registry operations varies according to the location of the server, its bit-type, and whether it is an in-process or out-of- process server. This section will give a brief description of the tools and
methods that can be used to clean the registry entries for a specific application.
Server Exe on the Server Machine All out-of-process servers created by Visual Basic recognize the command line switches UNREGSERVER and REGSERVER. These switches can be used for servers that are run locally or remotely. To clean the registry entries for
a server exe on the server machine:

Run the server with the command line switch /UNREGSERVER.

Run the server with the command line switch /REGSERVER.

Server Exe on a Client Machine
If the server application doesn't reside physically on a client machine, the CliRegXX tool should be used to unregister and reregister the server. The .vbr file and the .tlb file for the relevant server are needed for both operations. CliReg16 should be used for any 16-bit clients, regardless of the bit-type of the OS, and CliReg32 should be used for all 32-bit clients.
To use the client registration tool to unregister and register a remote server:

Run CliRegXX -u server.vbr -t server.tlb.

Run CliRegXX server.vbr -t server.tlb. A dialog box will appear to prompt for the name of the remote machine and the network protocol.


Server DLL (must be local)
DLL servers do not recognize the UNREGSERVER and REGSERVER parameters. To perform registry operations with in-process servers you must use the REGSVR32.EXE tool. RegSvr32 will query the DLL for the registry information needed and perform the operation specified (either a register or an unregister). To use:

Run RegSvr32 -u server.dll.

Run RegSvr32 server.dll.


Patricia G. Bajo
-----Mensaje original-----
De: Pezib Tinoco [mailto:pezib@unica.edu.ni]
Enviado el: Martes, 06 de Noviembre de 2001 06:39 p.m.
Para: visualbasic-esp@yahoogroups.com
Asunto: (VB-ESP) URGENTE!!!! Error al abrir un ADODB.Recordset

Hola a todos estoy tabando con VB6 y access 97, y al momento de abrir un ADODB.Recodset me indica un error.

El codigo que uso es el siguiente:

Dim rs As New ADODB.Recordset
rs.Open "select * from Estudiante where login ='" & Text1(0).Text & "'",db

donde db es una ADODB.Connection abierta, El error indica que el objeto no permite la automatizacion.

Algo interesante es que funciona en algunas maquinas(como la mia y 12 mas) y en otras no.

QUE HAGO?????

====================
Pezib J. Tinoco P.
UNICA,Nicaragua
505-02760004
Ext 5410
====================



Resumen Resumen

Visual Basic Página de Visual Basic

Página principal Página principal

www.jrubi.com