msaccess.exe generated errors

[MC]

This annoying error message from MS Access "MSACCESS.exe has generated
errors and will be closed by Windows. ... "
Keeps happening for most versions of MS Access like 95, 97, 2000, that I am
aware of.
On the web, I see that I am not the only one who have problem, sound like
there is a huge variable as a reason to this error.
As an IT staff, we have tried everything possibly we can to solve the
problem, but no success

Our ERP system front end design is Access, and back end is SQL 7 using ODBC
with a lot of table links...(I know it sounds stupid)
And randomly this error shows up, and closes the application.
Our best solution appears to be to change the ERP application, but this will
be a long proccess.
Anyone who have better idea, you are welcome to suggest
(Except the following ideas which we have tried: network issue,
computer/network card issue, Anti-virus interferenace, client, and server
named pipes priority, memory, speed...)
Thanks
MC

 

[Tony Toews]

This annoying error message from MS Access "MSACCESS.exe has generated
errors and will be closed by Windows. ... "
Keeps happening for most versions of MS Access like 95, 97, 2000, that I am
aware of.
On the web, I see that I am not the only one who have problem, sound like
there is a huge variable as a reason to this error.

Sure there are a lot of reasons why this error can occur. But to
point to Access 95, well known for being a product with a lot of
troubles, is stretching things just a bit.

As an IT staff, we have tried everything possibly we can to solve the
problem, but no success

How about Access 2003? MS realizes that crashes are highly
irritating and are doing their best to locate these problems with the
help of the Dr Watson reporting tool and fix these problems in the
next Service Pack. That said I suspect A2003 would be stabler than
the previous versions.

You can also use the runtime to run the app to avoid paying licensing
fees to MS for each copy of MS Access.

Our ERP system front end design is Access, and back end is SQL 7 using ODBC
with a lot of table links...(I know it sounds stupid)

Why? This sounds like an excellent solution. Although SQL 7 is
getting a bit out of date.

And randomly this error shows up, and closes the application.

No particular screen? Report? Some systems are more prone to this
error than others.

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

 

[MC]

We use Access 2000 at the moment, upgrading to Access 2003, Jet library, or
any other Windows Service pack (except SP1)
is out of the question. Our ERP will not accept it. (Their way of
controlling file version conflicts)

As for ERP, building front end ERP application with Access MDB libraries are
like building a car with Mercedes Engine and an old and rusty looking body.
Multi-user environment, ODBC connection and table links are not the greatest
and fastest connection to SQL, and too slow

No any other information, when the error occurs, just closes the MDB file
MC

 

[Tony Toews]

We use Access 2000 at the moment, upgrading to Access 2003, Jet library, or
any other Windows Service pack (except SP1)
is out of the question.

Ok, are you folks up to date on the Office 2000 patches at least?
Which is SP3. Also what version of Jet? This is the msjet40.dll in
the Windows system folder. Although I'm not at all sure how much in
detail that has to do with SQL Server.

Our ERP will not accept it. (Their way of
controlling file version conflicts)

Interesting that. A bit draconian I would say.

As for ERP, building front end ERP application with Access MDB libraries are
like building a car with Mercedes Engine and an old and rusty looking body.
Multi-user environment, ODBC connection and table links are not the greatest
and fastest connection to SQL, and too slow

<shrug> Lots of people are running Access just fine against SQL
Server. Although SQL Server 7 is getting to be a bit of an elderly
Mercedes.

What better development platform could you get that allows you to
create an app in such a short period of time?

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 Toews]

No any other information, when the error occurs, just closes the MDB file

But it's not like there's a particular pattern when this happens? As
in one or two particular forms or reports?

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

 

[MC]

Nothing obvious, it happens in various forms,
Using access and developing access would be fine for prototyping only. For
developping enterprize wide application, Viusal Basic, with ADO connection
would have been great for speed and performance, you don't want to have
Access VBA code and ODBC connection to handle and manipulate and do heavy
computing. Simple things yes...
MC

 

[Tony Toews]

Using access and developing access would be fine for prototyping only. For
developping enterprize wide application, Viusal Basic, with ADO connection
would have been great for speed and performance, you don't want to have
Access VBA code and ODBC connection to handle and manipulate and do heavy
computing. Simple things yes...

I guess we won't tell my client who has 25-30 users in all day long.
160 tables in the backend. 450 forms and 350 reports in the front
end. Yup, I guess Access is only for simple things.

This was an ERP system for a welding shop employing several hundred
welders. Materials, inventory, scheduling, massive QC, shipping and
invoicing.

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 Toews]

Nothing obvious, it happens in various forms,

You didn't answer my previous question about Access 2000 SPs.

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

 

[MC]

Office 2000 with SP1, windows 2000 with SP1 applied.
We use MSjet40.dll version 4.0.3714.7, size on disk 1,503,232 bytes
We tried lastest jet engine, which our application had problem with, as I
said before no any other service packs can be applied.

I guess we can say that developing our ERP system 6 years go, was the
cheapest, fastest solution to make big bugs by the Vendor.
You would not believe, the time my programmer(s) spent over 4 years to solve
bugs and errors in this application.
Thanks for the comment
MC

 

[Tony Toews]

Office 2000 with SP1, windows 2000 with SP1 applied.

Office 2000 with SP1? Chances are that MS has fixed most of the
crashes with SP3.

We use MSjet40.dll version 4.0.3714.7, size on disk 1,503,232 bytes

My msjet40.dll is 4.0.8618.0.

My standard advice is if you aren't on the latest Office/Access and
Jet SP with app crashing problems then there's not much we can do to
help.

MS really have worked hard on fixing crashing problems. MS looks
through the Dr Watson dumps they receive to figure out why it's
crashing. And those fixes are put in the SPs. Without the latest
SPs then I don't see what else we can do to help..

We tried lastest jet engine, which our application had problem with,

What kind of problems?

as I
said before no any other service packs can be applied.

I guess we can say that developing our ERP system 6 years go, was the
cheapest, fastest solution to make big bugs by the Vendor.
You would not believe, the time my programmer(s) spent over 4 years to solve
bugs and errors in this application.

I'm a little confused. You state that you developed your ERP system
and then you mention a vendor.

If you have access to the source code, which presumably you do, then
why are you even still dealing with the vendor? Unless, of course,
they have new versions of the software you folks want to install.

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 Toews]

We use MSjet40.dll version 4.0.3714.7,

That version of msjet40.dll is four years out of date.
http://support.microsoft.com/dllhelp/

But I'm not at all sure what is most important when it comes to
hitting a SQL Server 7 database. The Jet version or the MDAC version
or something else.

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

 

[MC]

I never said we developed this application.
We de-bug the application, but not in their native code,
we copy the code using their source code copier to custom library, and try
to fix it there.
They protect their actual libraries (MDB files).
Even if we had acces to their source, trying to re-code them in Visual
Basic, or .Net could take years for 2 programmer I have.
We are in the proccess of getting rid of this application, but finding,
implementing the right solution is not as easy as 1-2-3
(Months of testing, implementing, working parallel to existing system,
without down time to production...
It may take us a year to switch over and off course the Costs is ouch!

New version they have, they claim 80% .NET,
but when I saw their demo, I realised it is still too slow to open a lot of
forms, and they still use a lot of Access libraries, which I am hesitant
about
MC

 

[MC]

I missed to answer this part of your Question
*********

We tried lastest jet engine, which our application had problem with,

*******
When we install latest Jet and open any form or report in ERP, it would
start linking more then 400 SQL tables (where it normally links once or if a
link is missing)
We compile 15 access libraries (MDB file) whenever we have a code, or
application change on the client (again using their resource kit) test it
then push it to server.

Compiling normally solves this kind of linking issue, but in this case id
did not.
MC