Strange SP3 crash

[Brian]

I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly & predictably
crashes during development under certain circumstances but not in the live
environment (which are SP1 or SP2). The crash generates an ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:

On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>

I don’t think the code is at fault, though, for several reasons:

1. I use an almost identical procedure for record navigation in every form
in the app, and no others crash. If I add MsgBox “Test†after the Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after removing
the MsgBox “Test†I inserted above to test preventing the crash (i.e. “unable
to save form†and “not enough memory available to perform the operationâ€).

These versions of msaccess.exe work with no crash:

11.0.6355.0 SP1 5/18/04
11.0.6566.0 SP2 7/7/05

I can even copy these over the SP3 version, leaving the rest of SP3 intact,
and have it work correctly. This one, however, crashes:

11.0.8166.0 SP3 5/10/07

This is true also of stations running Access 2003 runtime; those with the
SP3 version of msaccess.exe crash, while those running earlier versions do
not.

Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do I have
to pursue a hotfixe from MS?

 

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

wait a second.. you have a DB that crashes.. and you just think that
MS is going to randomly give you a personalied hotfix??

ROFL

jeez, who are _YOU_ sleeping with, to get that kinda service??

I'd just reccomend moving to SQL Server, kid. WinFs is going to
replace NTFS soon.. and let's just suffice to say-- that no matter
what happens- SQL Server will continue to be ten times faster & better
than Access

-Aaron

 

[Brian]

1. It is not just a DB that is crashing. In fact, from my fairly extensive
testing, it is a particular version of msaccess.exe that crashes under
certain circumstances. Had you read my entire post carefully, you might have
understood that.
2. I have never considered a bug fix a personalized hotfix.
3. This would not be the first hotfix that MS has generated specifically as
a result of my discovery of an Access bug.
4. I'm not a kid, except perhaps to you, and then only if you are a
quintagenarian with a superiority complex over everyone five years your
junior.
5. I seem to have missed something in my development background - your part
about developing a front end in SQL server. I somehow got the impression that
SQL server was the back end and I had to have an application development
environment to develop a front end: .NET, Access, VB, C+, etc.. Strange,
indeed. Would you care to demonstrate a front end you have written on SQL
server?
6. You did not even attempt to answer my question, thus wasting my time and
possibly that of others who might actually want to contribute somethng useful
to the discussion.

Please have the courtesy to treat these forums with enough respect to at
least try to be helpful and not waste my time and that of the MVP's and
others who volunteer their time and knowledge to to share their expertise
with us non-experts.

wait a second.. you have a DB that crashes.. and you just think that
MS is going to randomly give you a personalied hotfix??

ROFL

jeez, who are _YOU_ sleeping with, to get that kinda service??

I'd just reccomend moving to SQL Server, kid. WinFs is going to
replace NTFS soon.. and let's just suffice to say-- that no matter
what happens- SQL Server will continue to be ten times faster & better
than Access

-Aaron

I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly & predictably
crashes during development under certain circumstances but not in the live
environment (which are SP1 or SP2). The crash generates an ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:

On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>

I don't think the code is at fault, though, for several reasons:

1. I use an almost identical procedure for record navigation in every form
in the app, and no others crash. If I add MsgBox "Test" after the Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after removing
the MsgBox "Test" I inserted above to test preventing the crash (i.e. "unable
to save form" and "not enough memory available to perform the operation").

These versions of msaccess.exe work with no crash:

11.0.6355.0 SP1 5/18/04
11.0.6566.0 SP2 7/7/05

I can even copy these over the SP3 version, leaving the rest of SP3 intact,
and have it work correctly. This one, however, crashes:

11.0.8166.0 SP3 5/10/07

This is true also of stations running Access 2003 runtime; those with the
SP3 version of msaccess.exe crash, while those running earlier versions do
not.

Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do I have
to pursue a hotfixe from MS?

 

[aaron_kempf]

yah; well I've got bugs _IN_ product studio that those fat lazy
bastards never fixed.

They said they would-- but then they chickend out.

Access is a crappy friggin database, kid.
Everyone around here blames it on the network; on the design-- on the
users; etc

The _REAL_ problem is that Access isnt' reliable enough for a half
dozen users and 25mb of data.
And Microsoft won't do anything to fix it.

Microsoft hasn't given MDB any new functionality int he past 15
years.. what makes you think that they give a crap about Jet?

1. It is not just a DB that is crashing. In fact, from my fairly extensive
testing, it is a particular version of msaccess.exe that crashes under
certain circumstances. Had you read my entire post carefully, you might have
understood that.
2. I  have never considered a bug fix a personalized hotfix.
3. This would not be the first hotfix that MS has generated specifically as
a result of my discovery of an Access bug.
4. I'm not a kid, except perhaps to you, and then only if you are a
quintagenarian with a superiority complex over everyone five years your
junior.
5. I seem to have missed something in my development background - your part
about developing a front end in SQL server. I somehow got the impression that
SQL server was the back end and I had to have an application development
environment to develop a front end: .NET, Access, VB, C+, etc.. Strange,
indeed. Would you care to demonstrate a front end you have written on SQL
server?
6. You did not even attempt to answer my question, thus wasting my time and
possibly that of others who might actually want to contribute somethng useful
to the discussion.

Please have the courtesy to treat these forums with enough respect to at
least try to be helpful and not waste my time and that of the MVP's and
others who volunteer their time and knowledge to to share their expertise
with us non-experts.

:

wait a second.. you have a DB that crashes.. and you just think that
MS is going to randomly give you a personalied hotfix??

jeez, who are _YOU_ sleeping with, to get that kinda service??

I'd just reccomend moving to SQL Server, kid.  WinFs is going to
replace NTFS soon.. and let's just suffice to say-- that no matter
what happens- SQL Server will continue to be ten times faster & better
than Access

-Aaron

I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly & predictably
crashes during development under certain circumstances but not in the live
environment (which are SP1 or SP2). The crash generates an ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:
On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>
I don't think the code is at fault, though, for several reasons:
1. I use an almost identical procedure for record navigation in every form
in the app, and no others crash. If I add MsgBox "Test" after the Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after removing
the MsgBox "Test" I inserted above to test preventing the crash (i.e. "unable
to save form" and "not enough memory available to perform the operation").
These versions of msaccess.exe work with no crash:
11.0.6355.0     SP1     5/18/04
11.0.6566.0     SP2     7/7/05
I can even copy these over the SP3 version, leaving the rest of SP3 intact,
and have it work correctly. This one, however, crashes:
11.0.8166.0     SP3     5/10/07
This is true also of stations running Access 2003 runtime; those with the
SP3 version of msaccess.exe crash, while those running earlier versions do
not.
Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do Ihave
to pursue a hotfixe from MS?- Hide quoted text -

- Show quoted text -

 

[aaron_kempf]

and my fave frontend for SQL Server- it's called Access Data
Projects. It makes everything-- uh-- Access easy.

I've written hundreds. Been doing SQL Server fulltime for almost a
decade.
It's just that I'm the only one -- knowledgable in SQL -- that gives a
rats ass about the poor helpless kids that didn't make it into Noahs
Ark (SQL Server)

-Aaron

1. It is not just a DB that is crashing. In fact, from my fairly extensive
testing, it is a particular version of msaccess.exe that crashes under
certain circumstances. Had you read my entire post carefully, you might have
understood that.
2. I  have never considered a bug fix a personalized hotfix.
3. This would not be the first hotfix that MS has generated specifically as
a result of my discovery of an Access bug.
4. I'm not a kid, except perhaps to you, and then only if you are a
quintagenarian with a superiority complex over everyone five years your
junior.
5. I seem to have missed something in my development background - your part

about developing a front end in SQL server. I somehow got the impression that
SQL server was the back end and I had to have an application development
environment to develop a front end: .NET, Access, VB, C+, etc.. Strange,
indeed. Would you care to demonstrate a front end you have written on SQL
server?
6. You did not even attempt to answer my question, thus wasting my time and
possibly that of others who might actually want to contribute somethng useful
to the discussion.

Please have the courtesy to treat these forums with enough respect to at
least try to be helpful and not waste my time and that of the MVP's and
others who volunteer their time and knowledge to to share their expertise
with us non-experts.

:

wait a second.. you have a DB that crashes.. and you just think that
MS is going to randomly give you a personalied hotfix??

jeez, who are _YOU_ sleeping with, to get that kinda service??

I'd just reccomend moving to SQL Server, kid.  WinFs is going to
replace NTFS soon.. and let's just suffice to say-- that no matter
what happens- SQL Server will continue to be ten times faster & better
than Access

-Aaron

I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly & predictably
crashes during development under certain circumstances but not in the live
environment (which are SP1 or SP2). The crash generates an ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:
On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>
I don't think the code is at fault, though, for several reasons:
1. I use an almost identical procedure for record navigation in every form
in the app, and no others crash. If I add MsgBox "Test" after the Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after removing
the MsgBox "Test" I inserted above to test preventing the crash (i.e. "unable
to save form" and "not enough memory available to perform the operation").
These versions of msaccess.exe work with no crash:
11.0.6355.0     SP1     5/18/04
11.0.6566.0     SP2     7/7/05
I can even copy these over the SP3 version, leaving the rest of SP3 intact,
and have it work correctly. This one, however, crashes:
11.0.8166.0     SP3     5/10/07
This is true also of stations running Access 2003 runtime; those with the
SP3 version of msaccess.exe crash, while those running earlier versions do
not.
Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do Ihave
to pursue a hotfixe from MS?- Hide quoted text -

- Show quoted text -

 

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

Ok.. Now honestly-- This crap:
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark

it just doesn't work anymore. This has not been the reccomended way
of doing things for a long time.

You requery for -- get this-- just the records you _WANT_.
It's called 'working with a db _SERVER_'.

Welcome to the 90s.

Just use a SQL statement.. Don't filter.. or page through jack shit.
Just set a SQL statement _DOG_.

-Aaron

 

[Gina Whipp]

Brian,

Hold out for an answer by someone REALLY wishing to answer your question,
which might mean reposting. Sorry for the inconvience that might cause you.
Aaron's answer to EVERYTHING is SQL Server whether right or wrong and with
no regard to what your REAL question is, which I see you have gathered by
your answer!

I do know there are several reported issues with SP3. Try searching on that
in these newsgroups you'll might find the answer you are looking for. Sorry
I couldn't be of more help, while I have Access 2007 I have not used it
enough yet to spot any bugs!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

1. It is not just a DB that is crashing. In fact, from my fairly extensive
testing, it is a particular version of msaccess.exe that crashes under
certain circumstances. Had you read my entire post carefully, you might
have
understood that.
2. I have never considered a bug fix a personalized hotfix.
3. This would not be the first hotfix that MS has generated specifically
as
a result of my discovery of an Access bug.
4. I'm not a kid, except perhaps to you, and then only if you are a
quintagenarian with a superiority complex over everyone five years your
junior.
5. I seem to have missed something in my development background - your
part
about developing a front end in SQL server. I somehow got the impression
that
SQL server was the back end and I had to have an application development
environment to develop a front end: .NET, Access, VB, C+, etc.. Strange,
indeed. Would you care to demonstrate a front end you have written on SQL
server?
6. You did not even attempt to answer my question, thus wasting my time
and
possibly that of others who might actually want to contribute somethng
useful
to the discussion.

Please have the courtesy to treat these forums with enough respect to at
least try to be helpful and not waste my time and that of the MVP's and
others who volunteer their time and knowledge to to share their expertise
with us non-experts.

wait a second.. you have a DB that crashes.. and you just think that
MS is going to randomly give you a personalied hotfix??

ROFL

jeez, who are _YOU_ sleeping with, to get that kinda service??

I'd just reccomend moving to SQL Server, kid. WinFs is going to
replace NTFS soon.. and let's just suffice to say-- that no matter
what happens- SQL Server will continue to be ten times faster & better
than Access

-Aaron

I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly &
predictably
crashes during development under certain circumstances but not in the
live
environment (which are SP1 or SP2). The crash generates an
ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:

On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>

I don't think the code is at fault, though, for several reasons:

1. I use an almost identical procedure for record navigation in every
form
in the app, and no others crash. If I add MsgBox "Test" after the
Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after
removing
the MsgBox "Test" I inserted above to test preventing the crash (i.e.
"unable
to save form" and "not enough memory available to perform the
operation").

These versions of msaccess.exe work with no crash:

11.0.6355.0 SP1 5/18/04
11.0.6566.0 SP2 7/7/05

I can even copy these over the SP3 version, leaving the rest of SP3
intact,
and have it work correctly. This one, however, crashes:

11.0.8166.0 SP3 5/10/07

This is true also of stations running Access 2003 runtime; those with
the
SP3 version of msaccess.exe crash, while those running earlier versions
do
not.

Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do I
have
to pursue a hotfixe from MS?

 

[Dirk Goldgar]

I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly & predictably
crashes during development under certain circumstances but not in the live
environment (which are SP1 or SP2). The crash generates an
ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:

On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>

I don’t think the code is at fault, though, for several reasons:

1. I use an almost identical procedure for record navigation in every form
in the app, and no others crash. If I add MsgBox “Test†after the Selector
=
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after
removing
the MsgBox “Test†I inserted above to test preventing the crash (i.e.
“unable
to save form†and “not enough memory available to perform the operationâ€).

These versions of msaccess.exe work with no crash:

11.0.6355.0 SP1 5/18/04
11.0.6566.0 SP2 7/7/05

I can even copy these over the SP3 version, leaving the rest of SP3
intact,
and have it work correctly. This one, however, crashes:

11.0.8166.0 SP3 5/10/07

This is true also of stations running Access 2003 runtime; those with the
SP3 version of msaccess.exe crash, while those running earlier versions do
not.

Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do I
have
to pursue a hotfixe from MS?

I don't know what is causing your crash, but there is a post-SP3 hotfix,
which may or may not cure it. Have a look here:

http://support.microsoft.com/kb/945674
Description of the Access 2003 post-Service Pack 3
hotfix package: December 18, 2007

 

[Brian]

That hotfix resolved the problem Dirk. Thank you for good solid information,
as usual. Also thank you for wading through the other comments to deal with
my actual problem.

1. It is not just a DB that is crashing. In fact, from my fairly extensive
testing, it is a particular version of msaccess.exe that crashes under
certain circumstances. Had you read my entire post carefully, you might have
understood that.
2. I have never considered a bug fix a personalized hotfix.
3. This would not be the first hotfix that MS has generated specifically as
a result of my discovery of an Access bug.
4. I'm not a kid, except perhaps to you, and then only if you are a
quintagenarian with a superiority complex over everyone five years your
junior.
5. I seem to have missed something in my development background - your part
about developing a front end in SQL server. I somehow got the impression that
SQL server was the back end and I had to have an application development
environment to develop a front end: .NET, Access, VB, C+, etc.. Strange,
indeed. Would you care to demonstrate a front end you have written on SQL
server?
6. You did not even attempt to answer my question, thus wasting my time and
possibly that of others who might actually want to contribute somethng useful
to the discussion.

Please have the courtesy to treat these forums with enough respect to at
least try to be helpful and not waste my time and that of the MVP's and
others who volunteer their time and knowledge to to share their expertise
with us non-experts.

wait a second.. you have a DB that crashes.. and you just think that
MS is going to randomly give you a personalied hotfix??

ROFL

jeez, who are _YOU_ sleeping with, to get that kinda service??

I'd just reccomend moving to SQL Server, kid. WinFs is going to
replace NTFS soon.. and let's just suffice to say-- that no matter
what happens- SQL Server will continue to be ten times faster & better
than Access

-Aaron

I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly & predictably
crashes during development under certain circumstances but not in the live
environment (which are SP1 or SP2). The crash generates an ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:

On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>

I don't think the code is at fault, though, for several reasons:

1. I use an almost identical procedure for record navigation in every form
in the app, and no others crash. If I add MsgBox "Test" after the Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after removing
the MsgBox "Test" I inserted above to test preventing the crash (i.e. "unable
to save form" and "not enough memory available to perform the operation").

These versions of msaccess.exe work with no crash:

11.0.6355.0 SP1 5/18/04
11.0.6566.0 SP2 7/7/05

I can even copy these over the SP3 version, leaving the rest of SP3 intact,
and have it work correctly. This one, however, crashes:

11.0.8166.0 SP3 5/10/07

This is true also of stations running Access 2003 runtime; those with the
SP3 version of msaccess.exe crash, while those running earlier versions do
not.

Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do I have
to pursue a hotfixe from MS?

 

[Brian]

Yes. I must admit I was more than a little sarcastic in my original response
to Aaron. Dirk got me the hotfix info though, and it solved my problem, so
I'm back in business.

Brian,

Hold out for an answer by someone REALLY wishing to answer your question,
which might mean reposting. Sorry for the inconvience that might cause you.
Aaron's answer to EVERYTHING is SQL Server whether right or wrong and with
no regard to what your REAL question is, which I see you have gathered by
your answer!

I do know there are several reported issues with SP3. Try searching on that
in these newsgroups you'll might find the answer you are looking for. Sorry
I couldn't be of more help, while I have Access 2007 I have not used it
enough yet to spot any bugs!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

1. It is not just a DB that is crashing. In fact, from my fairly extensive
testing, it is a particular version of msaccess.exe that crashes under
certain circumstances. Had you read my entire post carefully, you might
have
understood that.
2. I have never considered a bug fix a personalized hotfix.
3. This would not be the first hotfix that MS has generated specifically
as
a result of my discovery of an Access bug.
4. I'm not a kid, except perhaps to you, and then only if you are a
quintagenarian with a superiority complex over everyone five years your
junior.
5. I seem to have missed something in my development background - your
part
about developing a front end in SQL server. I somehow got the impression
that
SQL server was the back end and I had to have an application development
environment to develop a front end: .NET, Access, VB, C+, etc.. Strange,
indeed. Would you care to demonstrate a front end you have written on SQL
server?
6. You did not even attempt to answer my question, thus wasting my time
and
possibly that of others who might actually want to contribute somethng
useful
to the discussion.

Please have the courtesy to treat these forums with enough respect to at
least try to be helpful and not waste my time and that of the MVP's and
others who volunteer their time and knowledge to to share their expertise
with us non-experts.

wait a second.. you have a DB that crashes.. and you just think that
MS is going to randomly give you a personalied hotfix??

ROFL

jeez, who are _YOU_ sleeping with, to get that kinda service??

I'd just reccomend moving to SQL Server, kid. WinFs is going to
replace NTFS soon.. and let's just suffice to say-- that no matter
what happens- SQL Server will continue to be ten times faster & better
than Access

-Aaron




I have an app that crashes on Access 2003 SP3, but not on SP1 or SP2. I
discovered this because I develop on SP3 and it repeatedly &
predictably
crashes during development under certain circumstances but not in the
live
environment (which are SP1 or SP2). The crash generates an
ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:

On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>

I don't think the code is at fault, though, for several reasons:

1. I use an almost identical procedure for record navigation in every
form
in the app, and no others crash. If I add MsgBox "Test" after the
Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after
removing
the MsgBox "Test" I inserted above to test preventing the crash (i.e.
"unable
to save form" and "not enough memory available to perform the
operation").

These versions of msaccess.exe work with no crash:

11.0.6355.0 SP1 5/18/04
11.0.6566.0 SP2 7/7/05

I can even copy these over the SP3 version, leaving the rest of SP3
intact,
and have it work correctly. This one, however, crashes:

11.0.8166.0 SP3 5/10/07

This is true also of stations running Access 2003 runtime; those with
the
SP3 version of msaccess.exe crash, while those running earlier versions
do
not.

Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do I
have
to pursue a hotfixe from MS?

 

[Tony Toews [MVP]]

Dirk got me the hotfix info though, and it solved my problem, so
I'm back in business.

Glad to hear that helped.

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/

 

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

Ginas answer for everything is an obsolete database called JET.

Brian,

Hold out for an answer by someone REALLY wishing to answer your question,
which might mean reposting.  Sorry for the inconvience that might cause you.
Aaron's answer to EVERYTHING is SQL Server whether right or wrong and with
no regard to what your REAL question is, which I see you have gathered by
your answer!

I do know there are several reported issues with SP3.  Try searching on that
in these newsgroups you'll might find the answer you are looking for.  Sorry
I couldn't be of more help, while I have Access 2007 I have not used it
enough yet to spot any bugs!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

1. It is not just a DB that is crashing. In fact, from my fairly extensive
testing, it is a particular version of msaccess.exe that crashes under
certain circumstances. Had you read my entire post carefully, you might
have
understood that.
2. I  have never considered a bug fix a personalized hotfix.
3. This would not be the first hotfix that MS has generated specifically
as
a result of my discovery of an Access bug.
4. I'm not a kid, except perhaps to you, and then only if you are a
quintagenarian with a superiority complex over everyone five years your
junior.
5. I seem to have missed something in my development background - your
part
about developing a front end in SQL server. I somehow got the impression
that
SQL server was the back end and I had to have an application development
environment to develop a front end: .NET, Access, VB, C+, etc.. Strange,
indeed. Would you care to demonstrate a front end you have written on SQL
server?
6. You did not even attempt to answer my question, thus wasting my time
and
possibly that of others who might actually want to contribute somethng
useful
to the discussion.

Please have the courtesy to treat these forums with enough respect to at
least try to be helpful and not waste my time and that of the MVP's and
others who volunteer their time and knowledge to to share their expertise
with us non-experts.

"a a r o n . k e m p f @ g m a i l . c o" wrote:

discovered this because I develop on SP3 and it repeatedly &
predictably
crashes during development under certain circumstances but not in the
live
environment (which are SP1 or SP2). The crash generates an
ntdll.dll-related
1000 error in the event log. There are different places where the crash
occurs. Here is one example:
On Error GoTo ErrorHandler
If IsNull([Selector]) = True Then Exit Sub
Me.RecordsetClone.FindFirst "[CustomerID] = " & [Selector]
Me.Bookmark = Me.RecordsetClone.Bookmark
LastName.SetFocus
Selector = Null
<Crashes here>
I don't think the code is at fault, though, for several reasons:
1. I use an almost identical procedure for record navigation in every
form
in the app, and no others crash. If I add MsgBox "Test" after the
Selector =
Null line, then it does not crash.
2. I have done many compact/repairs
3. I have even imported the form to a new DB, all to no avail.
4. I also get strange errors when attempting to save the form after
removing
the MsgBox "Test" I inserted above to test preventing the crash (i.e.
"unable
to save form" and "not enough memory available to perform the
operation").
These versions of msaccess.exe work with no crash:
11.0.6355.0     SP1     5/18/04
11.0.6566.0     SP2     7/7/05
I can even copy these over the SP3 version, leaving the rest of SP3
intact,
and have it work correctly. This one, however, crashes:
11.0.8166.0     SP3     5/10/07
This is true also of stations running Access 2003 runtime; those with
the
SP3 version of msaccess.exe crash, while those running earlier versions
do
not.
Does anyone have a post-SP3 hotfix or version of msaccess.exe, or do I
have
to pursue a hotfixe from MS?- Hide quoted text -

- Show quoted text -

 

[Simon Dickson]

I am having the same problem you posted about and was wondering if you had had any success in solving this problem.

Cheers
Simon