MS Access 97 db via network share not returning records.

[Microsoft]

Good day.

We are using a legacy Access 97 db and are accessing this remotely via a
network share mapped drive.
I will refer to the access server as the machine hosting the access db and
remote as the remotely connecting machine.

I can open up the database on the remote machine via MS Access 2003 and it
squacks about compatibility as expected, but does allow me to change data
and run the same select query I try to run through a VB6 app. It returns
records (.recordcount > 0)

If I now try to run this same query via a VB6 app connecting through the
mapped drive, no errors are thrown by the ADODB.Connection.Execute method
but no records are returned.

What could be causing this?

Thanks in advance.
ws

 

[George Nicholson]

Are you using any non-vb functions in the query (Custom functions or NZ
which is Access-only)?

 

[WireStealth]

No sir...the query is a simple:
SELECT * FROM Modem WHERE [PhoneNo] = '25555'
which works on the remote box when issued through MS Access but not when
issued through VB.
At first I thought is was a simple network mapping permissions issue, but I
see the access server mdb file opened with a ldb lock file, so I know I can
connect and open the database.

Thanks for the quick reply.

 

[George Nicholson]

Just a guess, which is easy enough to test: specify each field (i.e., don't
use *)


--
HTH,
George

No sir...the query is a simple:
SELECT * FROM Modem WHERE [PhoneNo] = '25555'
which works on the remote box when issued through MS Access but not when
issued through VB.
At first I thought is was a simple network mapping permissions issue, but
I see the access server mdb file opened with a ldb lock file, so I know I
can connect and open the database.

Thanks for the quick reply.

 

[a a r o n . k e m p f]

you should use SQL Server.

Access MDB is not a real database.. it is more like a spreadsheet.

HTH

-Aaron

 

[a a r o n . k e m p f]

And by the way.. 'Access Server' is a bad name.. Becuase Access
doesn't support working against a Server.

If you want an environment that 'just works' then move to SQL Server.
If you want to be able to utilize the latest and greatest in hardware
and software-- then move to SQL Server.

-Aaron

 

[George]

By default, the ADO execute method does NOT display errors unless you use
the dbFailOnError option. In other words, it's a "silent failure" scenario.

This is true in VBA, at least. I've not tried this in VB6, but it should be
the same.

George

 

[George]

Hmm. You really want to say that the reason an ADOB.Connection.Execute
method fails from VB6 is that Access is "more like a spreadsheet"?

Could you elaborate a bit on the logic BEHIND that assertion? Or better yet,
cite a reference to that effect. I'm just dying to know how you arrived at
thtat conclusion.


message
you should use SQL Server.

Access MDB is not a real database.. it is more like a spreadsheet.

HTH

-Aaron

 

[a a r o n . k e m p f]

I disagree.

Only a ****ing dipshit would use the CurrentProject.Connection.Execute
without realizing that.

Have you ever heard of Docmd.RunSql??

Or making commands?

-Aaron

 

[a a r o n . k e m p f]

I'm saying that JET is retarded; as is anyone that uses it.

It doesn't support multiple users-- Even Tony Toews-- the most
oprtimistic obsolete JET JUNKIE anywhere around here-- agrees that Jet
can't handle more than 10-12-15 people writing and inserting at the
same time.

That _COMPLETELY_ reinforces everything that I've been saying for the
past decade.

If your cry baby database doesn't support multiple users.. then move
to a database will BALLS that supports multiple users.

SQL Server rocks.. it is by far the best engine for MS Access

-Aaron

 

[Tony Toews [MVP]]

If I now try to run this same query via a VB6 app connecting through the
mapped drive, no errors are thrown by the ADODB.Connection.Execute method
but no records are returned.

You can't run a Select query using the Execute. Execute is for action
queries. You can open a recordset against a Select query. Now note
that I'm not that experienced with ADODB and VB6 using database apps
so I sure could be wrong.

Please post the line(s) of code with which you are running the query.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[George Hepworth]

Aaron.

At least you're touting Microsoft products, so there might be some hope for
you yet.

Yet, my question remains unaddressed: Do you really want to say that the
reason an ADOB.Connection.Execute
method fails from VB6 is that Access is "more like a spreadsheet"?

 

[David W. Fenton]

You can't run a Select query using the Execute. Execute is for
action queries. You can open a recordset against a Select query.
Now note that I'm not that experienced with ADODB and VB6 using
database apps so I sure could be wrong.

I'm pretty sure you're wrong where ADO is concerned.

 

[WireStealth]

Thanks for the suggestion but unfortunately that didn't do it either .

Anything else at all that you can think of?

Best Regards,

Just a guess, which is easy enough to test: specify each field (i.e.,
don't use *)


--
HTH,
George

No sir...the query is a simple:
SELECT * FROM Modem WHERE [PhoneNo] = '25555'
which works on the remote box when issued through MS Access but not when
issued through VB.
At first I thought is was a simple network mapping permissions issue, but
I see the access server mdb file opened with a ldb lock file, so I know I
can connect and open the database.

Thanks for the quick reply.

Are you using any non-vb functions in the query (Custom functions or NZ
which is Access-only)?

--
HTH,
George


Good day.

We are using a legacy Access 97 db and are accessing this remotely via
a network share mapped drive.
I will refer to the access server as the machine hosting the access db
and remote as the remotely connecting machine.

I can open up the database on the remote machine via MS Access 2003 and
it squacks about compatibility as expected, but does allow me to change
data and run the same select query I try to run through a VB6 app. It
returns records (.recordcount > 0)

If I now try to run this same query via a VB6 app connecting through
the mapped drive, no errors are thrown by the ADODB.Connection.Execute
method but no records are returned.

What could be causing this?

Thanks in advance.
ws