Comiling problems

From: Leslie Isaacs (leslie_at_gppayroll.net)
Date: 03/31/04 

Date: Wed, 31 Mar 2004 14:59:44 +0100

Hello All

I have posted a problem this morning on the 'Multi-user' newsgroup, but
there have been further developments that lead me to suspect that the
problem is connected to the compiling of modules. I have copied the original
post to the end of this one in case it is needed.

The 'further development' is that I have just tried going into a module and
selecting debug > compile all modules. This resulted in a 'compile error -
variable not defined' message, with the 'stLinkCriteria' part of the
following function (contained in a Class Module) being highlighted:

Private Sub Command628_Click()
On Error GoTo Err_Command628_Click

    Dim stDocName As String

    stDocName = "frm select months"
    DoCmd.OpenForm stDocName, , , stLinkCriteria

Exit_Command628_Click:
    Exit Sub

Err_Command628_Click:
    MsgBox Err.Description
    Resume Exit_Command628_Click

End Sub

While in that module, if I click the the Compile Loaded Modules icon, no
errors are reported.

Is it likely that this problem is the cause of a very severe performance
problem that has recently come about (see earlier post, copied below)?

Hope someone can help
Many thanks
Les

My original post was:
I have an A2K 'backend' mdb on one PC, and 4 other
networked PCs each with a 'frontend' mdb that uses linked
tables from the 'backend'.

All has been working fine for over a year now, except that
both the backend and the frontends had become bloated and
would not 'unbloat' much by compacting and repairing. I
tried creating a new mdb and importing the tables from the
backend, and the result was a much smaller mdb, so I did
the same with the frontend, linking the tables from the
new (smaller) backend, and the new frontend was again much
smaller.

So I was happy: until I found that performance has become
inordinately slow - all forms take at least 10 seconds to
open, and many take 1-2 minutes (previously the max was 10
seconds). I have tried compacting, repairing and
refreshing the links using the linked table manager, but
all to no effect.

What's happening - and what can I do?

Many thanks
Les

Relevant Pages

  • Re: Comiling problems
    ... (No private e-mails, please) ... > networked PCs each with a 'frontend' mdb that uses linked ... > tables from the 'backend'. ... > tried creating a new mdb and importing the tables from the ...
    (microsoft.public.access.modulesdaovba)
  • Re: Multi users Logon Security questions
    ... > The next thing I need to do is split the database so others can work ... and navigate to the mdb - copy the mdb. ... You can use your desktop shortcut (which will open your frontend). ... Ctrl-O and open the backend mdb. ...
    (microsoft.public.access.security)
  • Re: Creating a Temporary Table/RecordSet in Multi-User Database
    ... The 'backend' mdb (contains just ... A copy of the 'frontend' mdb would sit on ... It appears that exclusivity is set by each user. ...
    (microsoft.public.access.security)
  • Re: Adding a database to existing workgroup file
    ... Some don't even need the mdw to do so. ... the frontend on each person's PC. ... links to the tables in the backend. ... the database splitter on a secure mdb - the backend will end up unsecured. ...
    (microsoft.public.access.security)
  • Re: Design problem : security layers
    ... I'd like to reuse the Objects i write for the frontend in the backend, ... So for the moment what i do is having two packages, ... the credit sub-package will contain all that behaviour that ...
    (comp.lang.java.programmer)