Need help with Access

  • Thread starter Thread starter Jens Egil Evensen
  • Start date Start date
J

Jens Egil Evensen

This thread has been posted earlier, but I have not got an
answer that solves the problem, and it's kind of urgent...
So I try again.

I have developed a rather complex application for the
Norwegian government, using Access 2000 format database
aand application-file. When I open the database on a
Windows XP with Office XP SP2 (probably others too), the
Access application remains in the process-list even though
the window is closed. I had this problem earlier in the
developing stage, but then I discovered that if I replaced
calculated fields using the DSum function, the problem was
fixed. But.... Now the problem is back.. I know that you
can get this problem if you uses objects from other
libraries, and don't close them properly, but I'm sure
that is not the case here.
The symptoms are as follows:
-When Access is closed, the temporary files (.ldb) remains
in the application folder.
-MSAccess is still in the processlist in task anager.
-If i try to open access nothing happens.
-If I try to open access application that have a dialogbox
of some kind in the startupprocedures,...it appears on the
screen!!! But the access application and menus doesn't
appear.
-If I kill the access process in the taskmanager and then
opens the application, everything works fine.

It looks like the Applications starts but nothing shows up
on the screen...

Could this e a bug in Microsoft Access? I do not have the
problem using the same application on a computer with
office 2003 installed.

I also use DLookup in several fields in the forms.. could
that be the reason? Some bug in the Built-in functions?

I hope you guys can help...

Best regards
Jens Egil Evensen
..
 
Jens,

[...]
The symptoms are as follows:
-When Access is closed, the temporary files (.ldb) remains
in the application folder.
Click to expand...

Can you exclude that there are open recordsets or other references when you
close the DB? Example:

Dim Rst As Recordset
Set Rst = ...
....
Rst.Close
Set Rst=Nothing

Do you always close and destroy references?

Peter
 
Can you exclude that there are open recordsets or other
references when you
close the DB?
Click to expand...

Yes, I always close the reference. To be honest, I think
this problem occures because I'm using some built-in
functions in the application (ie. DLookup and Dsum), but I
can't say for sure. But one thing indicates a bug in the
used version: I works perfectly in MS Access 2003.
 
Back
Top