|
| |
|
|
|
|
Remember - When using
our systems, pressing F1 at any time pops-up a context sensitive help screen
| Archive Contracts/Contractors (ces
vers 6.1d on) - Top of Page - To
prevent Orders or Notices being raised or assigned to old Contracts/Contractors Sets of
Rates make sure you check the archive tick box against their respective record
(Records/Payments). |
| Contract Payment Reports (commitments) - Top of Page - CES correctly
includes all orders and notices with a SCHEDULED date up to and including the end date of
the last defined payment period for the specified contract. In this way orders raised on
the system but not due for completion by the end of the current financial year will NOT be
included as committed amounts (they fall into next years budget). If you wish to
override this normal configuration and extend the date by which committed Orders/Notices
are to be included - simply create a new/dummy payment period with your required extended
end date (records/payments/contract details - payment periods). |
| Deleting Sites
- Top of Page - Sites
with attached Operations/Provisional work may NOT be deleted until all child records have
been removed (this is by design- to prevent accidental deletion of records). TIP
- Rather than deleting the site it might be better to simply archive the site by
re-assigning it to a holding contract - off-line (see
New Sites off-Line). In this way if the site should come back on-line in the
future all that is required is to re-assign the sites contract. |
| Modify Cost Centre Code
- Top of Page - Cost
Centre Codes once allocated may still be modified by high security users however, the
database must first be locked. To modify, lock the database, access cost centres via
Records/Basic Codes/Cost Centres, then change the cost centre code as required. If
the code is not unique no change will be made. |
| Modify Job Codes - Top of Page - Until a Job Code
(operation) has been booked in the Asset Register the Job Code itself may be changed
within CES - for your protection, once used in the Asset Register Job Codes may only be
modified using CESMod. |
| Multiple Contractor Evaluations
(ces vers 6.1d on) - Top of Page - A
report has been provided to display multiple contractors prices on full contract
evaluations. The report is found at Reports/Asset Register/Contract Analysis, then
select by Job Type/Job Code. After selecting the contract to evaluate CES will allow
you to select whether you wish to display a multi-contractor evaluation, answer yes and
select as many sets of rates as you wish to display/calculate on the report. Each
operation will list the contractor reference and appropriate schedule of rate along with
cost per annum. At the bottom of the report each contractors overall assessment will
be displayed. |
| Sites with a Specified Operation
- Top of Page - To
find sites with a specified operation use the Asset Register Report - List Sites.
When asked the question - Report Options - choose select Site Listing, when asked choose
the option ONLY sites used in the Asset Register, you will next have an option to decide
whether you want to list sites for a specified operation, answer yes...... and next select
the operation. |
| New Sites Off-Line
- Top of Page - To
create Sites and add Operations off-line simply create a dummy contract and contractor ie.
Create a new contractor code 99 with no schedule of rates, and new contract say 99 awarded
to contractor 99. Create new sites as required but assign the site to contract 99.
When the site goes live simply modify the sites assigned contract to the required
live contract...... this method in reverse could also be used to temporarily take a site
off-line. You can still assess site costs by running any asset register
evaluation for contract 99 but when asked for contractor rates to test select a live set
of rates (rather than the default contractor 99). |
| Overall Operation Quantities (ces
vers 6.1d on) - Top of Page - Most
clients need to return information about total quantities (across all contracts) for
statistical analysis by various bodies. A report has been enhanced to provide this
facility - Reports/Asset Register/List Operations, select Operation Details and then
Overall Quantities. |
Windows95 Disk Caching/Redirector
- Top of
Page -
It is important to note that the updated VREDIR.VXD workstation fix is also required for
stable operations when using Windows 95 workstations. There are actually two different
operating-system-level functions at work when using combinations of Windows 95 and Windows
NT workstations and Windows NT server: local buffering of data at the Windows 95
workstations (controlled
by VREDIR.VXD and its registry settings at the workstation) and opportunistic-locking
buffering at the Windows NT workstations (controlled by combinations of settings at the
workstation and server, but only supported by disabling it at the server). To download the
latest redirector patch use the Microsoft link above.
Disabling Windows 95 Disk Caching
Select My Computer
Select System
Choose Performance Tab
Click on File System Button
Check Disable write-behind caching for all drives
|
Windows
NT Disk Caching - Top
of Page -
RFCB (File Handles Caching) and Opportunistic Locking
Microsoft introduced an operating system feature in Windows NT that caches file handles
called RFCB Caching. This was done in order to increase the file handling performance of
specific kinds of Windows based applications on an NT server (such as client/server based
applications).
This feature can cause problems in traditional DOS based database programs that use
Standard File and Record Locking (using SHARE.EXE or SHARE.386), such as Solution System 2
or CaseBASE. This problem has also been reported in programs written in dBASE, Clipper and
Microsoft's own Access and Foxpro.
The technical explanation of this is as follows: the NT Server service caches file handles
(RFCBs) associated with files it has opened on behalf of a client (workstation) request.
Although write requests proceed normally, close requests are acknowledged by the server,
but are buffered from the file system. This is intended to optimize response time to
repeated open/close operations performed by clients (which Solution System 2 and CaseBASE
do a great deal of). Additionally, Opportunistic Locking (oplock)
is an optimisation that is a logical extension of the way a client caches its own file
close request and relies on the server to arbitrate future requests for file access by
other clients, rather than allowing the application to actually close it's own file
handles. In many situations, Oplocks must also be disabled for compatibility purposes.
Because of Opportunistic Locking's relationship with file closes, RFCB Caching and
Opportunistic Locking go hand-in-hand.
Microsoft presumes you will not be running traditional DOS database applications on your
new server and as a result, both of these potentially data corrupting features are
activated by default upon installation of Windows NT Server.
An obvious sign that a file is being held open is the reported file size may be zero. In
Control Panel, the Server option displays open files, when in fact, they are only open by
the Server service in a cached mode. Other signs may include sharing violations or data
and index file corruption, or at least an apparent lack of synchronisation between the
data at various workstations. Solution System 2 and CaseBASE rely on the file handles
actually being closed. Local file operations are not serviced by the server
and are not subject to RFCB Caching.
To disengage both opportunistic locking and RFCB Caching, make the following modifications
using the Registry editor (REGEDT32.EXE in Windows NT Server 3.51, and REGEDIT.EXE in
Windows NT Server 4.0). Note that only your
qualified service representative should do this.
Verify (and correct, if necessary) these NT Server parameters:
EnableOpLockForceClose REG_DWORD set to 1 (default=0)
EnableOplocks REG_DWORD set to 0 (default=1)
CachedOpenLimit REG_DWORD set to 1 (default=0)
--------------------------------------------------------------------------------
Step 1
Choose: HKey_Local_Machine ->
System ->
Current Control Set ->
Services ->
LanmanServer ->
Parameters ->
If the value EnableOpLockForceClose exists
Double-click on it, or select it, then pull down "Edit"
and choose DWORD ->
In DWORD Editor, Hex selected, enter the value 1
Or, if the value EnableOpLockForceClose does NOT exist
Pull down "Edit" and choose Add value ->
Value name: EnableOpLockForceClose ->
Data type : REG_DWORD ->
Press OK ->
In DWORD Editor, Hex selected, enter the value 1
--------------------------------------------------------------------------------
Step 2
Choose: HKey_Local_Machine ->
System ->
Current Control Set ->
Services ->
LanmanServer ->
Parameters ->
If the Value EnableOpLocks exists
Double-click on it, or select it, then pull down "Edit"
and choose DWORD ->
In DWORD Editor, Hex selected, enter the value 0
Or if the value EnableOpLocks does NOT exist
Pull down "Edit" and choose Add value ->
Value name: EnableOpLocks ->
Data type : REG_DWORD ->
Press OK ->
In DWORD Editor, Hex selected, enter the value 0
--------------------------------------------------------------------------------
Step 3
Choose: HKey_Local_Machine ->
System ->
Current Control Set ->
Services ->
LanmanServer ->
Parameters ->
If the value CachedOpenLimit exists
Double-click on it, or select it, then pull down "Edit"
and choose DWORD ->
In DWORD Editor, Hex selected, enter the value 1
Or, if the value CachedOpenLimit does NOT exist
Pull down "Edit" and choose Add value ->
Value name: CachedOpenLimit ->
Data type : REG_DWORD ->
Press OK ->
In DWORD Editor, Hex selected, enter the value 1
--------------------------------------------------------------------------------
After these changes have been made, shut down your server and start it back up. These
changes will not take effect until you do this!
When running Windows NT Server, it is very important that you ensure that you have applied
all the current service packs from Microsoft. Microsoft maintains a free download site at
http://www.microsoft.com/msdownload/default.htm.
If you are not familiar with doing this, contact your hardware and software vendor to do
it for you.
|
| User Directory Open Error
- Top of Page - Refers
to our old dos version of CES. Windows NT when daylight saving alters the date/time
stamp for the file userform.dbs. You must manually reset the date/time stamp
of this file to 01/06/92 and time to 03:14:16 (am).
|
- Top of Page - |
|
|
|
|