R
Ragnar Midtskogen
Hello,
I wrote and maintain an Access 2000 applicaton which uses SQL Server 2000 as
back-end through ODBC linked tables.
As I make changes to the objects and the VBA code in the client, the size of
the mdb file tends to grow, even though I compact on close.
The file is currently around 7+ MB, but when I install an update at the
client's lab it gets compacted to around 4 MB.
I usually bring back a copy of the compated file and for a while it stays
relatively small.
I develop on Windows 2000 Professional and Windows XP Professional,
accessing the server with the SQL Server DB through VPN.
At the client's workstation machines all run Windows 2000 Professional. The
machine where the SQL Server is running, that is a Windows Server 2000.
Does anyone know what causes this odd behavior? I am not aware of any
problems due to this, I am just curious if there is anything I could do to
my machines to have the file compact to the same size.
Any comments appreciated,
Ragnar
I wrote and maintain an Access 2000 applicaton which uses SQL Server 2000 as
back-end through ODBC linked tables.
As I make changes to the objects and the VBA code in the client, the size of
the mdb file tends to grow, even though I compact on close.
The file is currently around 7+ MB, but when I install an update at the
client's lab it gets compacted to around 4 MB.
I usually bring back a copy of the compated file and for a while it stays
relatively small.
I develop on Windows 2000 Professional and Windows XP Professional,
accessing the server with the SQL Server DB through VPN.
At the client's workstation machines all run Windows 2000 Professional. The
machine where the SQL Server is running, that is a Windows Server 2000.
Does anyone know what causes this odd behavior? I am not aware of any
problems due to this, I am just curious if there is anything I could do to
my machines to have the file compact to the same size.
Any comments appreciated,
Ragnar