B
Brigitte P
I have the strangest thing in my database that runs for many years
completely trouble free but I noticed today that saving of records is
inconsistent or exceptional slow. The database is FE on local machine, BE on
server (Windows 2000 on local machines, recently converted from NT, and NT
on the server until conversion can take place). The database was developed
in A97 and is now converted to A2002 FE and BE.
When I make a change in a record FE and check in the BE shortly thereafter,
the change did not take, but it shows in the FE that the change is done.
When I check a little while later in the BE (without closing the BE), the
change is sometimes there and sometimes is not. A user entered a piece of
data this morning on her FE which did not show on BE at all (she usually
makes a change and quickly closes her FE). However, when she pulled up her
record hours later, the change showed in the FE even though it wasn't in the
BE.
Seems to me that the saving operation to the server is severely delayed and
sometimes can't take place at all. I refreshed all links, repaired and
compacted and checked my dbase forms and queries, but all seems to be fine
(and was for years) I'm completely puzzled. Maybe it is of importance that
our server seemed very slow today (which our IT folks say has to do with
traffic on the server), but also the drive on the server is near to full. I
wonder if there is simply not enough space for the saving operation which
would be a disaster because we run many, many databases like the one above
and may not catch problems in time.
Please can anyone shed some light on this.
Brigitte P.
completely trouble free but I noticed today that saving of records is
inconsistent or exceptional slow. The database is FE on local machine, BE on
server (Windows 2000 on local machines, recently converted from NT, and NT
on the server until conversion can take place). The database was developed
in A97 and is now converted to A2002 FE and BE.
When I make a change in a record FE and check in the BE shortly thereafter,
the change did not take, but it shows in the FE that the change is done.
When I check a little while later in the BE (without closing the BE), the
change is sometimes there and sometimes is not. A user entered a piece of
data this morning on her FE which did not show on BE at all (she usually
makes a change and quickly closes her FE). However, when she pulled up her
record hours later, the change showed in the FE even though it wasn't in the
BE.
Seems to me that the saving operation to the server is severely delayed and
sometimes can't take place at all. I refreshed all links, repaired and
compacted and checked my dbase forms and queries, but all seems to be fine
(and was for years) I'm completely puzzled. Maybe it is of importance that
our server seemed very slow today (which our IT folks say has to do with
traffic on the server), but also the drive on the server is near to full. I
wonder if there is simply not enough space for the saving operation which
would be a disaster because we run many, many databases like the one above
and may not catch problems in time.
Please can anyone shed some light on this.
Brigitte P.