[AccessD] Error 3043 Disk or Network Error in runtime

Tue Dec 9 12:12:38 CST 2008

Does the re-boot cure it?

If it is all on the same PC then it may be that the installation of Access
itself was done over a network.

Max

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: 09 December 2008 17:42
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Error 3043 Disk or Network Error in runtime

Hi Max,

Since the app FE & BE normally install in the same folder we don't use UNC
for our paths.  The relinker first looks in the app folder and if it sees
the BE it just links.  The error I have seen when the tables don't link in
other databases is something else having to do with table not being where it
is supposed to be.  This has me puzzled because the module that is throwing
the error is passed the relinker stage.  I tend to agree with Gustav that
the problem is external to the app, but I have not been able to find any
references to similar situations.  We have seen other dll registration
issues cause problems, but not this one.  There was a virus going around
quite a few years ago that affected the dll that handles windows long file
names. When the virus hit a computer our program started throwing an error.
Turns out we found lot of infections. I am wondering if this is something
similar. Just need to narrow down where to look.

Thank you for your thoughts.

Doug 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Tuesday, December 09, 2008 9:26 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Error 3043 Disk or Network Error in runtime

Doug,
Whenever I get this it has ALWAYS been that the network has thrown an error
and the FE can no longer "See" the BE.  A reboot has always fixed it.
If you system is using a network path then regardless of where the FE/BE
reside, then it will traverse the network.  A typical path for me is
\\server\z\data\mymdb.mdb

HTH
Max

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy
Sent: 09 December 2008 16:54
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Error 3043 Disk or Network Error in runtime

Folks,

We distribute an application as an Access 2002 runtime.  The installation is
done with Wise/Sagekey.  We have many copies of the application out. One of
our clients just installed the application and is getting an Access vba
error 3043 "Disk or Network Error".  This is a front/back end application
and both are on the same computer in the same folder. After the first report
of the problem I thought is was a bad installation so logged onto the
customers computer remotely, did a complet un-install of the application and
runtime and with a new installationg file re-installed it. Still get the
error.  The location of the error indicates that the relinker has run and we
are looking at the computers location settings to set our date, currency and
address masks to match. The routine that is breaking follows.  We have not
seen this problem before and I am wondering if there could be a dll
coruption, or missing somewhere. The operating system is Windows XP.

I look forward to your thoughts.

Doug

Code follows: (tFM is a user defined type declared at the module level)

Public Sub GetCountrySettings()
Dim rs As DAO.Recordset
Dim db As DAO.Database
Dim sSQL As String
Dim sCountrySettings As String
Dim fld As Field
Dim LCID As Long

  LCID = 0  'GetSystemDefaultLCID()

   On Error GoTo GetCountrySettings_Error

      sCountrySettings = GetUserLocaleInfo(LCID, LOCALE_SCOUNTRY)
      tFM.sCountry = sCountrySettings

      If Not IsNull(sSQL) Then
            sSQL = "Select * From tblUserFormat Where fldCountry = '" &
sCountrySettings & "'"
            Set db = CurrentDb
            Set rs = db.OpenRecordset(sSQL, dbOpenForwardOnly)
            For Each fld In rs.Fields
                  Select Case fld.Name
                        Case "fldDateMask"
                              tFM.sDateMask = fld.Value & ""
                        Case "fldDateFormat"
                              tFM.sDateFormat = fld.Value & ""
                        Case "fldPhoneMask"
                              tFM.sPhoneMask = fld.Value & ""
                        Case "fldPhoneFormat"
                              tFM.sPhoneFormat = fld.Value & ""
                        Case "fldTimeMask"
                              tFM.sTimeMask = fld.Value & ""
                        Case "fldTimeFormat"
                              tFM.sTimeFormat = fld.Value & ""
                        Case Else

                  End Select
            Next

      Else
            'Leave as is
      End If

GetCountrySettings_Exit:
   On Error GoTo 0
      Set rs = Nothing
   Exit Sub

GetCountrySettings_Error:

      MsgBox "Error " & Err.Number & " (" & Err.Description & ") in
procedure GetCountrySettings of Module basInternational"
    Resume GetCountrySettings_Exit:
End Sub

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com