Using MetCal Without MetTrack

[Hawaii596]

If migrating to use of another database, how do you configure MetCal to query and send other than to MetTrack?  Or what workarounds has anyone figured out?  When you use an instrument in a MetCal procedure, it looks in MetTrack for the ID # to be sure it is in calibration.  It asks you to enter the ID # of the item being calibrated and verifies it is in MetTrack.

What workarounds has anyone figured out to bypass this?  I can see putting in a standard ID # and setting that up in a minimal MetTrack database.  But where to send the data from the calibration....?? That is the tough one. 

Kind of bottom line, how do you implement MetCal when using a database other than MetTrack, with the least amount of problems/issues?

[CalLabSolutions]

We have been helping customers do this for years..

We created and HOW TO a few years back..
https://docs.google.com/a/callabsolutions.com/document/d/1WBA2RCKgq7sOZhLR0Cqc0oQeP4Xhc2w-5Z9AAFuN9Qc

Mike..

PS.. If the link does not work for you let me know. 

[Hawaii596]

Thank you Mike.  Already passed it on.  I am not the programmer, but passed it on to those people.  I'll post if further questions.  Thanks again.

[CalLabSolutions]

Glad I could help..

[measure]

What does Fluke say about it?

[CalLabSolutions]

Never Asked!
I know this method has it's pros and cons.  But from my experience most customers don't us MET/TRACK.  If all they want is the calibration results from the automation this give them exactly that.

Mike