Access & ODBC WBEM problem

[Vern007]

Linking to SMS Tables through Access results in only one row of data being returned. Apparently a hotfix from MS fixes this. I got the hotfix but linking tables to an Access 2000 database still doesnt work. I've heard of this problem before but can't seem to find an answer. Check out

http://www.swynk.com/friends/hobbs/...SMS Tables through Access results in only one

for a description.

Has anyone else experienced this? Am I doing something wrong? I would like to try running some reports with Access but can't get it to work. Any suggestions would be of help.

Thanks.

 

[snyderj]

Is this true for all your linked SMS tables? This may sound like a dumb question, but do you know for sure that there is more than one record in the SMS database? Can you open the SQL Server table and verify the records?

Q267598 (

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q267598)

is specifically for WHERE DATETIME criteria, so just opening the table should return all available rows.

Have you tried deleting and re-linking the tables?

Are you using Access 2000?

Do you have only one database open at a time? If you try WBEM ODBC links to one particular table name at multiple SMS sites in one Access database, or in multiple Access databases open at the same time, Access will cache the server\table connection information and provide you the same data. (In other words, if you opened a table x on server A, then table x on server B you'll see the data from table x on server A.)

Is you %systemdir%\wbemdr32.dll version 1.50.1085.0006?


snyderj

 

[Vern007]

Yes I do have more than one record. I can view the tables in SQL and see the data. I have tried countless tables and still only get one record. Only one database is open at a time.
If it helps, I'm running SMS 2 SP3 on a W2K Server SP2 with SQL 2000 SP2.

I am using Access 2000. Is there an issue there?

Other reporting methods (Web Reports, Crystal Info, SnapReports demo version) work fine so it is not due to a lack of data.

wbemdr32.dll ver. 1.50.1085.27

Any thoughts???

V

 

[snyderj]

I have no idea what the issue is, but here are a couple more thoughts.

Have you tried either opening your .mdb on another PC, and/or creating a new .mdb on your PC or another PC?

Are you viewing the table directly from the Tables object (not from a query)? If from a query, perhaps a limiter is in place.

You could try re-loading WBEMODBC (W2K CD at ValuAdd\MSFT\MGMT\WBEMODBC).

You could try accessing the records through Excel (Data > Get External Data > New Database Query

 

[Vern007]

You could try re-loading WBEMODBC (W2K CD at ValuAdd\MSFT\MGMT\WBEMODBC).


DOH!
Reloading the WBEM ODBC driver from the Win2K CD seems to have fixed the glitch.

Thanks snygerj for the help.