Anyone know what could be the cause?

[Hey]

I've got an A2K based program that I've been working with for a few years.
It's split BE (on shared system over P2P network) with each user having
their own FE. About 40 tables, 250 queries, 10 macros and about 50 forms
with some having subforms, about 200 different reports some with subreports.

All current updates/patches have been applied to office and A2K over time.

Lately I've noticed that a user will be working away and all of a sudden the
program disappears. User is staring at the desktop, with nothing running.
They can immediately go back in the program and all seems fine, but what's
up? Why would a system do this? It's not like it errors out--it just
disappears.

I've tried to duplicate this, and have found with the most recent 2 or 3
version updates about the last 2 months of changes to code/additions of
reports, etc., that this will happen sporatically. It doesn't happen,
usually...but every so often...bang! At the desktop (I use a machine where
FE and BE are on same computer). Click the program icon to run on the same
computer, and same keystrokes used, and everything is fine. Then, an hour
or 2 later...bang. Back at the desktop. I can't track it to any specific
button, routine, macro, code, etc. It'll work fine for 10 minutes, or an
hour, or 5 hours, then on something that's worked fine before...bang.
Desktop.

I've tried decompiling program, recompiling and then packing. Several
times. Same results. It'll work for awhile with no problem and then
bang...desktop.

Very frustrating, in that I can't find ANY similarity in what is causing the
problem.

I look in the folder where the program resides and after the program ceases
operation the .ldb file is left there. Plus, the .ldb file for the data file
is in that folder as well. I can just click either ldb file and delete
them. Just thought I'd mention that if it helps anyone tell what the
problem could be.

Anyone point me in an appropriate investigative direction?

Thanks

 

[Dale Fye]

I had an application a while ago that had similar problems, but I was using
the api to hide the Access window, so I only had the forms on screen. Had a
couple of users that this happened to occassionally. After trying to
duplicate it, on my machine and others, without success, I just attributed
it to operator error. A couple of versions (of my application) later, and
after our migration to A2K3, this stopped happening. Never did figure out
what was causing it, although I had suspicions that it had to do with a
handled error that was causing some variable values to be lost.

However, what I did find was that Access was not closing when this happened.
So, I had to open the task manager, then go to the processes tab (Access
does not show up in the Applications tab if you have the application window
hidden), and end the process from there. Usually, that would delete the ldb
file, but not always.

Dale

 

[aaron.kempf]

it's called a crash..

if you use Jet-- you're asking for trouble.

Move to a stable database, it's really simple math.

Jet _SUCKS_.
SQL Server is the worlds most popular database, and it has been for
many years.

-Aaron

 

[Hey]

Hi Dale,

Unfortunately, I can't attribute the problems to "operator error" as you
were able to do. Different operators, different circumstances that work
sometimes and other times cause the drop out of the program. I can even get
mine to drop out, and I am, after all, a "perfect:" operator. ::big grin::

I'll try putzing with the program in another version of Access (I have 2003
here too) and see if it happens with that. Thanks for posting your
experience as I hadn't even thought of trying that. Possibly a nudge in the
right direction.

And I'll also try looking in the task manager too, next time it happens. I
hadn't thought of looking at that.

Thanks for the suggestions.

 

[Hey]

Actually, Aaron, I don't want to change everything I'm doing and the way I'm
doing it because of a glitch I've run into in the last couple weeks. I just
wanted suggestions from the MVPs here on what I might have screwed up
recently to cause this problem. I've been using A2K successfully to replace
some old DOS databases since about 2001 or so and it works fabulously.
Other than a few little glitches--and, when I get into it, I usually find
it's something I didn't understand about Access and so therefore I did
something in error.

That's what I'm looking for in this instance.

I've seen many of your posts and regardless of what is requested, your
solution is always to switch to SQL Server. Someone could have a database
on their laptop to keep track of the shoes in their closet and you'd have
them switch to SQL Server. I guess if you're a hammer, everything looks
like a nail, eh?


it's called a crash..

if you use Jet-- you're asking for trouble.

Move to a stable database, it's really simple math.

Jet _SUCKS_.
SQL Server is the worlds most popular database, and it has been for
many years.

-Aaron

 

[aaron.kempf]

well you should have changed it a long time ago.

so sorry that you made the wrong architecture decision-- just because
the MVPs are popular around here (in a JET newsgroup) that doesn't
mean that they're right.

Jet fucking sucks and anyone using it for any reason-- should be
_FIRED_ and then _SPIT_UPON_.

-Aaron

 

[aaron.kempf]

and for the record-- yes-- SQL Server works great on laptops.

Meanwhile Jet doesn't even work on the most popular flavor of Vista
(X64)

 

[a a r o n _ k e m p f]

and btw-- you're the one with a hammer-- everything looks like a
nail--
you're the one that is claiming that everyone should only use jet
(just because some fat lazy retard from canada doesn't have the IQ to
learn a real database)


you're the one that was building DOS-based databases (because you
don't know how to use a real database) and now you bless your clients
with more paperweights.

**** you.

move to SQL Server.

-Aaron