Results

Capfast database was defined by the project engineer

RDB parameters were entered by a technician

Reports generated for signal checkout from Access expedited the process

Changes required to classes of channels for labels, hardware type and engineering units could be done to 10’s or hundreds of records in seconds

Loading two databases slows the reboot time by about 10 seconds.

Having the source in two places requires more coordination.

Deleting or changing the names of existing records was the most difficult operation - it required locating and deleting the records in Access

The inconvenience for deleting records was more than compensated for by the ease of channel check out and ability to reconfigure many channels at once. The schematics are still the easiest way to understand a database.

Previous slide Back to first slide View graphic version

| LANL | Lansce | UC | DOE |

L O S A L A M O S N A T I O N A L L A B O R A T O R Y
Operated by the University of California for the US Department of Energy

Results

Capfast database was defined by the project engineer

RDB parameters were entered by a technician

Reports generated for signal checkout from Access expedited the process

Changes required to classes of channels for labels, hardware type and engineering units could be done to 10’s or hundreds of records in seconds

Loading two databases slows the reboot time by about 10 seconds.

Having the source in two places requires more coordination.

Deleting or changing the names of existing records was the most difficult operation - it required locating and deleting the records in Access

The inconvenience for deleting records was more than compensated for by the ease of channel check out and ability to reconfigure many channels at once. The schematics are still the easiest way to understand a database.

For problems or questions regarding this web site contact George Vaughn.