Notes
Premvet 5 Manual Pages
Cross Updating

Cross Updating Release Notes Doc Center FAQ's Manual

What is Transferred?

Automatically Transferred

During the normal operation of the system the following are transferred automatically by the system.

The work will automatically be logged, sent to the remote sites and will be added to appropriate records there.

Automatically Sent

As the user details are also common to all sites, any changes made to the password database will also be sent over to all sites to maintain a common set of users. This can cause confusion especially if staff at remote sites have access to the password Maintenance option and make chages.

The other files, that contain 'common' data will also be transferred if changed.

These are:

By default, the users and other common file will be sent, however, if you would rather have manual control over them then you can add an entry into the file /usr/utilities/x_ignore to tell the system NOT to send them. x_ignore is a text file one entry per line:

v6users.sys User and Password Details
doses1.dat Dose Details
v6apmt Dispensing Fees and Mileage Table

The names you should enter in this are:

To NOT send Passwords and users add v6users.sys
To NOT send Doses details add doses1.dat
To NOT send Dispensing Fees and Mileage table add v6apmt

Menu Options

There are two options to allow you to send other files, one menu is the 'Transfer Files' option in xmenu and the others are options within Premvet 5.

We will look at the Premvet 5 options first:

Stock Codes and Automatic Pricing

If your stock files have identical items at each e.g. Main site Penicillin is item 100 and Penicillin has the SAME number at the branch. You can send over all the prices from the main site to all the remote ones. The system will only send over: Description, Price, Supplier/Practice code, analysis, and dose details. It will NOT affect Quantity in stock, sales figures or ordering details.

With Doses and Warnings, only if the main site has either of these set will they update the branch. This allows for the branch systems to have some control over the doses they want but still allow for critical items to be controlled by the main system.

The option is:

Stock Control -> Utilities -> Price Increase -> Send to remote

This option will only appear at the main site.

The details will be extracted and the next time x_send is run they will be queued for the remote sites. The details will be extracted automatically at the remote site whenever x_check is run.

With Automatic Pricing you can use the option:

Auto-Pricing -> End of Year/Price Inc -> Send prices to remote

to send over all AP codes and prices - it will NOT send the times used figures - these are 'per branch'. The option is only visible at the main site.

The other menu option is within xmenu and unlike the above will give you the option to send via another medium rather than the modem.

Transfer files menu option

There may be a need to transfer some selected files from one machine to another. There is an option on xmenu that will allow you transfer some of the common files via modem, tape or floppy. When selected, the screen will show:

Premvet 5 Directory  = /u/vetdata
Sites to send to = pluto
You are = saturn

1 Automatic pricing files (See above)
2 Stock files  (See above)
3 Main Clinical files
4 Text editor definition files
5 Label layouts
6 Address/Telephone list
7 Laboratory files
8 User Names & ID's
9 None of the above (See below)
0 CSV files (See below)       S SQL Files (See below) 
P Premvet Parameters  (See below) 

R Extract from Tape/Floppy
Q Return to Main menu 

Please Type Letter of Your Selection and Press [ENTER]

Once you have made your selection the system will copy the required files to a temporary area and the screen will show:

Preparing transfer file wait ...
Once the transfer file has been prepared (this can take from seconds with one of the smaller options to 10's of minutes in the case of the clinical files). You will be asked how you want the data sent:

Total amount to transfer : 1558.2 Kbs.
Modem at 2400 baud 144 mins
Modem at 9600 baud  70 mins
Modem at 14.4 baud  27 mins
3.5 floppies  needed 2

1 Modem 
2 Tape
3 Zip Disk (/dev/zip)
4 Jaz Disk (/dev/jaz)
5 Floppy 3.5  A: (/dev/fd0135ds18)
6 Floppy 3.5  B: (/dev/fd1135ds18)
7 Secondary tape drive
Q Return to Main menu

Please Type Letter of Your Selection and Press [ENTER]
Once you select the method you will prompted for the media if appropriate or the work will be queued via the modem.

Notes:

The capacity for floppy disk is fairly small (1.4Mb), you may want to consider using Zip (100Mb) or Jazz (2Gb) disks if you are doing frequent updated. Additionally, you can copy the entire remote vet system onto a Jaz disk - this can then be run 'stand alone' on any other system. This allows you to manipulate and monitor remote systems from one server.

If you used tape or floppies you CANNOT add additional information to them. If you are transferring multiple items e.g. Stock AND automatic pricing files you will need two floppies or two tapes etc. You should use the 'Extract from tape/floppy' option to extract the data from the tapes/floppies when you reach the remote site. If you are using the modem then it will automatically be extracted at the remote end whenever x_check is run.

You will need to run x_check on the remote machine to collect the work. It is advisable that no-one is using the system while the transfer file is being prepared and that no-one is adding work while x_check is used on the remote machine.

There are certain files that once set-up should NEVER be transferred or copied over. These are: master.dev, param.exe and v6lf.

You should also be aware there are various log files, financial figures, etc. that are held with details on each site. While these are relatively unimportant you should avoid transferring them. In other words only transfer the files you require and not all of them.

One other point you will have to consider: If you are transferring files to alter the prices, add new procedures etc. then plan to transfer them back. Any work entered onto the main machine affecting these files whilst a copy is held remotely will be lost once the files are copied back on. You should carry out these procedures overnight or when little work is being added.

Many of the files are inter-related, you should group together files e.g. transfer all the stock files and not just individual ones. Otherwise you may have problems when accessing.

Other files

In some cases the options provided on the menu may not cover the range of files you wish to transfer. To meet this need there is a menu option 'None of the above'. When this option is selected you are prompted for the names of the files to transfer separated with a space. These files should be entered relative to the Premvet 5 data directory.

A list of the possible files that you may want to transfer are given below. The filenames given use the ? and * as the standard notation for wild-cards.

doses1.datDrug doses (will be sent automatically)
library.???Library data
macroSystem-wide macros
v6anacAnalysis codes
colour* eventsColour Events
v6users.sys User I.D. and passwords (will be sent automatically)
v6stpa Stock Parameters (See *note*)
param.exeGeneral Parameters (See *note*)
udef? uset?User Defined Files
breeds.hlp misc.hlpBreed and Poisons Help files
cost.datProcedure Costings Defaults
direct.datWritten Directives Defaults
email.datClient E-Mail addresses
os.datShifted Function Keys
filecapAttachments (Programs to use)
params.txtText Parameters
v6sbfiClinical Reports

*NOTE*: These items contain site specific data.
If you do transfer these make sure you check Branch Number (param.exe) and Supplier I.D. (v6stpa).

It is worthwhile considering copying all the information every few months. As we explained earlier, all the clinical information is transferred, but all it takes is for one of the transfers to fail and your databases are then different. It also keeps some of the minor files updated.

SQL scripts

If you have any Data-Major scripts you want to transfer then you can send individual scripts from here. Keep in mind all the scripts are usually associated with an index file (abc.idx), however, you cannot directly send the index files as this will clash with definition file indexes. You can get round this by creating a special Data-Major index starting with 'x'. Index files starting with x are taken as DM indexes and will be transferred.

You do need to specify the extension, so to send your xupdate index and the two scripts, pom1.sql and pom2.sql you would enter xupdate.idx pom1.sql pom2.sql

CSV Files and Premvet Parameters

Premvet has many 'lookup' tables containing Breeds, Colours, Species etc. used when adding/editing cards. These are stored in a 'site specific' file which means you cannot directly send that information to remote sites.

There is a Stand alone utility that will export the required table to a CSV file, this can then be sent with this option to the remote sites. You do not need to specify the extension e.g. to send species and canine breeds over you would enter xspecies xcabreed

The other option is to use the 'Premvet Parameter' option in xmenu, this will automatically run the appropriate Stand Alone utility for you and send the resulting CSV file for you.

When the csv file(s) are received by the remote it will automatically update the remote system. This allows you to maintain ONE set of master files and distribute the changes as needed.

See the FAQ: Sending Breeds etc. to Remote Sites for a step by step guide.

EXTRA/SUBFILES

One other method of transferring files, if you have a file you always want to send whenever x_send is run is to add it on the EXTRA line of call_info. The SUBFILES option allows you to send sepcific files only if they have changed. Refer to the utilities section for more information on this method.


Previous T.O.C. Next