By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,896 Members | 1,997 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,896 IT Pros & Developers. It's quick & easy.

MSACCESS.EXE - Application Error

P: n/a
DFS
I get these errors intermittently using a 3rd party COM object, under VB or
Access (in a module). These seem to be happening at a similar instruction
location.

Instruction at 0x77fcb032 referenced memory at 0xd18b4104. Memory could not
be "written"
Instruction at 0x77fcb7cf referenced memory at 0x00000000. Memory could not
be "written"
Instruction at 0x77fcbee8 referenced memory at 0xfffffffe. Memory could not
be "written"

Relevant pseudo-code:

1. Do Loop (ie 2000 times)
2. Dim obj as new ObjectType
3. response = obj.Method()
4. obj.close
5. Next

The errors always happen on the 3rd line. I've tried many variations of Dim
or Set and Close or Nothing. The code always crashes around the 500th
iteration, at the above memory locations.

Any ideas or explanations?

Thanks
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Fri, 24 Oct 2003 19:40:07 -0400, "DFS" <no******@nospam.com> wrote:

Contact the vendor. The second error is a null pointer assigment -
could be embarrasing for them.

-Tom.

I get these errors intermittently using a 3rd party COM object, under VB or
Access (in a module). These seem to be happening at a similar instruction
location.

Instruction at 0x77fcb032 referenced memory at 0xd18b4104. Memory could not
be "written"
Instruction at 0x77fcb7cf referenced memory at 0x00000000. Memory could not
be "written"
Instruction at 0x77fcbee8 referenced memory at 0xfffffffe. Memory could not
be "written"

Relevant pseudo-code:

1. Do Loop (ie 2000 times)
2. Dim obj as new ObjectType
3. response = obj.Method()
4. obj.close
5. Next

The errors always happen on the 3rd line. I've tried many variations of Dim
or Set and Close or Nothing. The code always crashes around the 500th
iteration, at the above memory locations.

Any ideas or explanations?

Thanks


Nov 12 '05 #2

P: n/a
While Tom's advice is certainly valid, I don't think the repeated Dim As New
statement is doing any good in your code.

Try:

1. Dim obj As ObjectType
2. Do Loop (ie 2000 times)
3. Set obj = New ObjectType
4. response = obj.Method()
5. obj.close
6. Set obj = Nothing
7. Next

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)

"DFS" <no******@nospam.com> wrote in message
news:vp************@corp.supernews.com...
I get these errors intermittently using a 3rd party COM object, under VB or Access (in a module). These seem to be happening at a similar instruction
location.

Instruction at 0x77fcb032 referenced memory at 0xd18b4104. Memory could not be "written"
Instruction at 0x77fcb7cf referenced memory at 0x00000000. Memory could not be "written"
Instruction at 0x77fcbee8 referenced memory at 0xfffffffe. Memory could not be "written"

Relevant pseudo-code:

1. Do Loop (ie 2000 times)
2. Dim obj as new ObjectType
3. response = obj.Method()
4. obj.close
5. Next

The errors always happen on the 3rd line. I've tried many variations of Dim or Set and Close or Nothing. The code always crashes around the 500th
iteration, at the above memory locations.

Any ideas or explanations?

Thanks

Nov 12 '05 #3

P: n/a
On Sat, 25 Oct 2003 11:45:02 GMT, "Douglas J. Steele"
<NOSPAM_djsteele@NOSPAM_canada.com> wrote:

Yes, DFS, please report back your findings. I think putting the Dim
statement outside of the loop has no effect in VBA. Unlike in other
languages where location does matter (e.g. C++, VB.NET).

Rather I would try something like:
response = obj.OtherMethod()
or
response = obj.Property
to see if the leak is located in Method or in the object's
initialization code.

-Tom.

While Tom's advice is certainly valid, I don't think the repeated Dim As New
statement is doing any good in your code.

Try:

1. Dim obj As ObjectType
2. Do Loop (ie 2000 times)
3. Set obj = New ObjectType
4. response = obj.Method()
5. obj.close
6. Set obj = Nothing
7. Next


Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.