Notes you need to take:

1) Ask user to quit the application as if user using the Execute file, you can't overwrite!

2) Copy All Work directory data and execute file to "Old" Subdirectory,
if found hard problem, just revert for safety!

3) You may found that you still can't overwrite execute file even all user has quit the application if you are using Novell!!
Try this in DOS mode:

Echo C| flag *.* +s -t [return]

Then, you can remove the transaction flag of execute file!


4) Copy the Database (.dbc, .dct, .dcx) if you have change view or do add/remove table!

5) Do Refill Job if you have change some table structure.
e.g. You have Increase the customer file CUST_NAME field from C(60) to C(100)
Since your client may input new data or update some information..
So, you need to do refill, sth like:

After copy the old customer to "OLD" directory and place the new customer at
working directory!!

set safety off
Use Customer Excl
zap
Append from Old\customer
use
set safety on

Then, the data is refilled to new structure table and you don't need to stop user before any structure change unless you have change the field name... ~_~"

P.s. Good LUck!! ^_~

---

>We have a customer trying to install a new build of an EXE we compiled, in a directory where there is an older build. According to the customer, the older EXE is not being replaced. What could cause this? I've already told my Customer Support guys to check whether the file is marked Read-Only. Is there something in the operating system that might prevent this?
>
>
>Thanks,
>Thomas Hirschman
>Microtime
>Chicago, Ill
>thomas@microtime.com