Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / December 2003

Tip: Looking for answers? Try searching our database.

NTVDM error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Pam - 12 Dec 2003 11:48 GMT
I have a visual basic 6.0 program on our network that
checks for updates to the Access FE.  If a new FE exists,
it is copied to the users local drive.  This program has
been in use for about 6 months with no problems.  However,
yesterday the exe file became corrupted twice.  The users
received the following error message.

The NTVDM CPU has encountered an illegal instruction.  
CS:0000 IP:0353 OP:f0 2b 8d 00 f0 Choose 'Close' to
terminate the application.

Does anyone know what might be causing this corruption?  
Thanks!
Cheryl Fischer - 12 Dec 2003 14:15 GMT
Here are a couple of references from Support.Microsoft.Com:

http://support.microsoft.com/default.aspx?scid=kb;en-us;245184

http://support.microsoft.com/default.aspx?scid=kb;en-us;156687

These may or may not apply to your situation.  Have you also posted your
question to one of the Visual Basic News Groups?  There may be more help
there.

--
Cheryl Fischer
Law/Sys Associates
Houston, TX

> I have a visual basic 6.0 program on our network that
> checks for updates to the Access FE.  If a new FE exists,
[quoted text clipped - 9 lines]
> Does anyone know what might be causing this corruption?
> Thanks!
Pam - 12 Dec 2003 17:38 GMT
Cheryl,

Thanks for the response.  I read these articles previously
and I don't think they apply.  My VB app is 32-bit vs 16-
bit.  I will also post the question in the VB forum as you
suggested.  Thanks.

>-----Original Message-----
>Here are a couple of references from Support.Microsoft.Com:
>
>http://support.microsoft.com/default.aspx?scid=kb;en-us;245184
>
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;156687

>These may or may not apply to your situation.  Have you also posted your
>question to one of the Visual Basic News Groups?  There may be more help
[quoted text clipped - 20 lines]
>
>.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.