Database communication not working

[Amy Blankenship]

That's a very interesting environment. We always want to see the error
messages and,
depending on the error, we will put in special handling.

Can you turn on all error messages for that user?

I have created a better diagnostic tool that should be able to shed more
light if I can get him to download and run it, or if there is another user
in the future with the same problem.

In the mean time, I have learned from this and will recommend to the client
that before we release the next course based on this template that he allow
me to add logic that logs ODBC error messages to a text file. That way, the
user still won't see it but it would be available in case of problems.

Thanks;

Amy

 

[Tony Toews [MVP]]

Precisely my feeling. That is why these errors are not displayed to the
user. This problem never once occurred in prerelease testing, and has only
occurred once in all the hundreds of users out there.

Correct. But the error handling routines are left in place so that if any errors
happen in the future the customer will see them.

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/

 

[Tony Toews [MVP]]

In the mean time, I have learned from this and will recommend to the client
that before we release the next course based on this template that he allow
me to add logic that logs ODBC error messages to a text file. That way, the
user still won't see it but it would be available in case of problems.

Yes, I've done similar on occasion myself although I logged them to the shared BE
database.

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/

 

[Amy Blankenship]

Yes, I've done similar on occasion myself although I logged them to the
shared BE
database.

If no communication is happening, then that's not going to work

Thanks;

Amy

 

[Amy Blankenship]

Correct. But the error handling routines are left in place so that if any
errors
happen in the future the customer will see them.

The user actually is told that no records were returned, which I felt at the
time was adequate.

-Amy

 

[Tony Toews [MVP]]

The user actually is told that no records were returned, which I felt at the
time was adequate.

But there should've been errors prior to that query running. In Access terminology
when you open the database Jet wouldn't find the database.

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/

 

[Amy Blankenship]

But there should've been errors prior to that query running. In Access
terminology
when you open the database Jet wouldn't find the database.

Yes I know but there are a lot of errors that occur that are expected.
Since all queries are done through one set of logic, to show errors in the
case of one failure would mean showing it in all cases, unless you
anticipate a particular error in advance. This one was not anticipated.
The open connection function I used does not have a separate error for
opening the connection. Instead, you simply get errors when the query is
executed.

-Amy

 

[Larry Linson]

That book has been out of print for ten years.

I'm under the impression that most/all of the information in that book is
still accurate, and just recently ordered a (used) copy via Amazon. I have
not received it, yet.

Larry Linson
Microsoft Access MVP

 

[David W. Fenton]

I'm under the impression that most/all of the information in that
book is still accurate, and just recently ordered a (used) copy
via Amazon. I have not received it, yet.

I assume you're talking about the Jet 3.5 version. All the
replication information is out of date in it (if you're working with
Jet 4), as well as it lacking all the new data types and features
added in Jet 4.

 

[Tony Toews [MVP]]

Yes I know but there are a lot of errors that occur that are expected.

And in Access you can gracefully deal with all those errors.

Since all queries are done through one set of logic, to show errors in the
case of one failure would mean showing it in all cases, unless you
anticipate a particular error in advance. This one was not anticipated.
The open connection function I used does not have a separate error for
opening the connection. Instead, you simply get errors when the query is
executed.

Then all I can say is the product you are using is not suitable for
the task.

And possibly you should be asking forums specific to that product as
to what the problems might be.

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/

 

[Amy Blankenship]

And in Access you can gracefully deal with all those errors.

I did. But unless you pass through all errors, then the unexpected ones are
exactly like all the others and get no special treatment because they are
unexpected.

Then all I can say is the product you are using is not suitable for
the task.

Certainly that connection component is less than perfect. But it has been
in use for over 10 years, and this is the first time I've heard of that
there was an issue because of that.

And possibly you should be asking forums specific to that product as
to what the problems might be.

I'm the person who would answer, were such a question to be posed on those
forums.

-Amy

 

[Tom Wickerqueer]

no such thing as a one-sized fits all?

you must not have used ADP; because 99% of the tedium with MDB goes away
when you graduate to ADP

 

[Tom Wickerqueer]

what could be wrong on the jet side?

the problem is that you're using jet.

it is a 2nd-rate database program from A to Z.

move to SQL Server

 

[Tom Wickerqueer]

I don't consider an MDB to be a database


move to SQL Server, bitch

and STFU about Access being buggy