IIRC, Wni98se has DCOM pre-installed in which case you shouldn't need to
install it again, support articles on DCOM are at (watch for wrapping).
http://support.microsoft.com/search/...&srchExtraQry=
DCOM has to be installed on a machine for ADO to work, having to install
DCOM as a separate step is only an issue with Win95 and Win98 machines.
--
Terry Kreft
MVP Microsoft Access
"MikeH" <mheden@bigfoot.com> wrote in message
news:1114499818.042970.154590@o13g2000cwo.googlegr oups.com...[color=blue]
> Terry,
>
> No, I just installed MDAC 2.7 - I didn't see anything in the
> documentation about installing DCOM first, and the MDAC installation
> didn't complain at all. I've since checked the version of DCOM on the
> Win 98SE machine - it is 'DCOM Win98 Gold 4.71.0.1719'.
>
> Should I install DCOM98 1.3, or am I clutching at straws here?
>
> Regards,
>
> Mike
>
>
>
> Terry Kreft wrote:[color=green]
> > Did you installl DCOM98 on the Win98 machine?
> >
> > This should have been done before you installed MDAC.
> >
> > --
> > Terry Kreft
> > MVP Microsoft Access
> >
> >
> > <mheden@bigfoot.com> wrote in message
> > news:1114421515.766471.112130@z14g2000cwz.googlegr oups.com...[color=darkred]
> > > Hello all,
> > >
> > > I'm using an Access 97 front-end with a SQL Server 2000 back-end.[/color][/color]
> One[color=green][color=darkred]
> > > particular bit of code runs a stored procedure to obtain a rowcount
> > > from one of the back-end tables. This works fine on one PC, but[/color][/color]
> not on[color=green][color=darkred]
> > > another. For the life of me, I can't see why it fails to work in[/color][/color]
> the[color=green][color=darkred]
> > > 'faulty' environment.
> > >
> > > This is the code:-
> > >
> > > Dim conImportCM As Connection
> > > Dim wrkODBC As Workspace
> > > Dim strConnection As String
> > > Dim qdf As QueryDef
> > >
> > > strConnection = "ODBC;DSN=ImportCM;Database=ImportCM;[/color][/color]
> UID=xxxx;[color=green][color=darkred]
> > > PWD=yyyy"
> > > Set wrkODBC = CreateWorkspace("", "", "", dbUseODBC)
> > > Set conImportCM = wrkODBC.OpenConnection("", dbDriverNoPrompt,[/color][/color]
> ,[color=green][color=darkred]
> > > strConnection)
> > > Set qdf = conImportCM.CreateQueryDef("", "{ ? = call
> > > prcCountViewContract}")
> > >
> > > qdf.Parameters(0).Direction = dbParamReturnValue
> > > qdf.Execute
> > >
> > > MsgBox "Row count is " & qdf.Parameters(0).Value
> > >
> > > The stored procedure that's being executed is:-
> > >
> > > CREATE PROCEDURE prcCountViewContract
> > > @Rows int = NULL OUTPUT
> > > AS
> > > SELECT ContractID FROM dbo.tblViewContract
> > > RETURN @@ROWCOUNT
> > > GO
> > >
> > > This works fine on one PC running Windows 2000 and returns the[/color][/color]
> expected[color=green][color=darkred]
> > > rowcount in the message box. On a another PC running Windows 98[/color][/color]
> SE, it[color=green][color=darkred]
> > > fails to return any data - the qdf.Parameters(0).Value returns[/color][/color]
> null.[color=green][color=darkred]
> > >
> > > Initially, I thought it might be a permissions issue (because this[/color][/color]
> is[color=green][color=darkred]
> > > running under a different user account on the two machines), but I[/color][/color]
> can[color=green][color=darkred]
> > > fire-up MS Query on the Windows 98 machine and manually run the[/color][/color]
> stored[color=green][color=darkred]
> > > procedure with 'exec prcCountViewContract' OK, so it looks like the
> > > Windows 98 environment has the correct access to the SQL Server
> > > back-end.
> > >
> > > I've also updated MDAC on the Windows 98 machine so that it's the[/color][/color]
> same[color=green][color=darkred]
> > > version as that used on the Windows 2000 PC (2.7). That has made
> > > absolutely no difference to the symptoms.
> > >
> > > Any ideas?
> > >
> > > Thanks,
> > >
> > > Mike
> > >[/color][/color]
>[/color]
