P
PatientCoder
I just got through reading a very informative thread entitled "The
Next Step". I am in a similar situation and I am a bit nervous as
well especially if the popularity of my app grows rapidly. My
application is a standalone developed in Access 2007 and will run on
home computers (no network involved). The app is split into BE and
FE. I have a couple of specific questions:
1. The BE database does not have excessive bloat but I imagine that I
should still run the R/C maybe once a month. I am worried about power
outages or someone turning of the computer during a Repair/Compact.
Could that become a support nightmare?
2. Does it make sense to deploy without a Repair/Compact process
built-in?
3. Are there any best practices for Repair/Compact and for recovering
from Repair/Compact aborts?
4. I've seem statements in some forums about Access 2007 runtime
causing problems if older version of Access is installed on the local
machine. Any thoughts on this? I want to distribute the app in
Access 2007 only...
Any suggestions would be appreciated.
Next Step". I am in a similar situation and I am a bit nervous as
well especially if the popularity of my app grows rapidly. My
application is a standalone developed in Access 2007 and will run on
home computers (no network involved). The app is split into BE and
FE. I have a couple of specific questions:
1. The BE database does not have excessive bloat but I imagine that I
should still run the R/C maybe once a month. I am worried about power
outages or someone turning of the computer during a Repair/Compact.
Could that become a support nightmare?
2. Does it make sense to deploy without a Repair/Compact process
built-in?
3. Are there any best practices for Repair/Compact and for recovering
from Repair/Compact aborts?
4. I've seem statements in some forums about Access 2007 runtime
causing problems if older version of Access is installed on the local
machine. Any thoughts on this? I want to distribute the app in
Access 2007 only...
Any suggestions would be appreciated.