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

The instruction at ... referenced memory at ... The memory cannot be "read"

P: n/a
I just distributed a FE mde file throught my department, and while stress
testing on the performance of the new release, 3 users got the following
error:

The instruction at ... referenced memory at ... The memory cannot be "read".

this seems like a computer-local problem as I cannot reproduce the same
error on any other computers

I tried running Dr. Watson (win2k) and it says "Exception number: c0000005
(access violation)"

and the last call was made to rtcAnsiValueBstr

any ideas?

Thanks!!

--
Message posted via http://www.accessmonster.com
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On Mon, 28 Feb 2005 22:16:36 GMT, "Justin To via AccessMonster.com"
<fo***@AccessMonster.com> wrote:

There is a small chance that this function rtcAnsiValueBstr is the
culprit. Post the code and we might be able to spot a potential
problem.
Otherwise these errors mostly occur because of mismatched components.
Run Windows update, and the latest service pack for Office, MDAC, and
Jet. Then try again.

-Tom.

I just distributed a FE mde file throught my department, and while stress
testing on the performance of the new release, 3 users got the following
error:

The instruction at ... referenced memory at ... The memory cannot be "read".

this seems like a computer-local problem as I cannot reproduce the same
error on any other computers

I tried running Dr. Watson (win2k) and it says "Exception number: c0000005
(access violation)"

and the last call was made to rtcAnsiValueBstr

any ideas?

Thanks!!


Nov 13 '05 #2

P: n/a
I tried debugging within VBA, and the error occurred on this line:

Set rs = db.OpenRecordset("SELECT .....")

Also, I never wrote a function called rtcAnsiValueBstr. Looking on the
internet, this function seems like it came with VB.

As for the updates, I'm not too sure if I could install them since we might
need Admin rights...are the updates necessary?

Thanks once again!

Justin

--
Message posted via http://www.accessmonster.com
Nov 13 '05 #3

P: n/a
On Tue, 01 Mar 2005 14:21:43 GMT, "Justin To via AccessMonster.com"
<fo***@AccessMonster.com> wrote:

The updates are critical IMHO.
We have an IT Networking branch in our company, and the technicians
sometimes still run into a Windows NT 4.0 SP0 server. And they wonder
why it's so slow? Or a workstation with more than 100 viruses on it.
Never been patched.

If your system administrator wants to retain the rights to install
service packs and updates, he/she will have to come by on a very
regular basis.

If I was the computer police, they would stop working if they hadn't
been patched in the last 90 days.

-Tom.

I tried debugging within VBA, and the error occurred on this line:

Set rs = db.OpenRecordset("SELECT .....")

Also, I never wrote a function called rtcAnsiValueBstr. Looking on the
internet, this function seems like it came with VB.

As for the updates, I'm not too sure if I could install them since we might
need Admin rights...are the updates necessary?

Thanks once again!

Justin


Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.