0

Types Procedure Tab

The help says that added files are stored in the dB. Does anybody know if that's accurate? I would think what's really stored in the dB is only the address of the file (i.e. a pointer / reference) rather than the actual executable itself. If the file is stored, then it has to be reloaded with each new revision & multiple copies of the executable exist at all times. If only the address is stored, the executable will alwys be current, but if the file is moved to another location, then the pointer in the dB needs to be updated.

13 comments

Date Votes
0
Avatar
Michael Johnston

From my understanding, the actual file is stored in the database, not a location. I don't quite follow what you mean that multiple copies would exist. You would replace a given executable with an updated one when a revision occurred. Only the current procedure would be stored.

0
Avatar
William Green

I believe the results are stored in the CallSheetReadings table. See Label Information.rpt in Custom Reports.

0
Avatar
William Green

Sorry, I misread the question.

0
Avatar
William Green

But I think the answer is the same. Everything is stored in tables, stored in the database. See the Label Information Report again. TypeFiles table.

0
Avatar
Lawrence Rodkey


I believe those tables just hold small amounts of informaton.  If you look at the data types shown in them, they are "char" , "int","nvarchar", and "numeric"  I don't beleve they can store a exe file.

 

I had a similar question regarding the .pro files.  Does the procedure need to be added to the database or just referenced in the procedure field with the exact name of the instrument line of procedure and then it goes and looks it up in the proc.dir?. 

 

Any tutorial on adding/running the old style procedure from MetTeam would be appreciated.  When I run it, Met Cal Runtime comes up saying it cannot find procedure.

 

Thanks

0
Avatar
Ben Brown

A PXE file is stored in the server that holds your database. A .pro file is stored in a separate location and is referenced by a .ini file that will go to the proc.dir that holds your procedures. Either your .ini file is not working correctly or your procedure is stored in Met Team incorrectly. I would go to the Editor and copy the procedure name exactly, then go to that procedure in Met Team and rename it with the copied information from the Editor.

 

0
Avatar
William Green

I can't remember which version of Met/Cal it happened. I do know when we changed from Met/Track to Met/Team, I could only run *.pxe files. I actually like this because a lot of the old problems I had, mainly directory crashes, went away. I now run all my procedures as pxe's from my Projects folder(s). Creating pxe's is easy. Open the procedure in Met/Cal Editor. Click File, New, Project from Existing Procedure. Name the project, It'll ask if you want to copy external files, I say Yes, it's up to you. In Editor, you can document various things by right clicking the Project name in Solution Explorer an entering the information needed. This depends on your QA requirements. The last thing to do is to click Build, Publish Package, and save the pxe to a Projects folder. I have never had a pxe procedure crash. I can store all of my required documentation right to the project folder. I think Fluke got it right with pxe's!

I hope I'm answering your question.

0
Avatar
david morgan

Exactly. One copy in the Executables folder, One copy in the dB. Two constitutes multiple.

0
Avatar
Michael Johnston

By executables folder, you mean the bin output from the solution? Or are you storing all your PXEs somewhere else? I don't think you'd want to be able to link MET/TEAM to the bin output, since changes wouldn't be validated in any way before they went live. Since you have to deliberately update the version that's in the database, it ensures that only those who should be doing so are the ones doing it.

0
Avatar
Lawrence Rodkey


Great suggestions....it ended up being a bug with the first release of 2.1.2.  Installed latest updates and works fine now.

0
Avatar
david morgan

The executables folder is where the techs browse to select at runtime.

0
Avatar
Michael Johnston

If you're storing the PXEs in MET/TEAM and setting up the procedure for the types, don't they run directly from the database? Admittedly I am stil using MET/BASE, so I don't know MET/TEAM well, but what I've investigated, that's what I thought the whole point was. I do know that with MET/CAL 9 you can stop techs from even being able to run an executable and force them to use what's in MET/TEAM.

0
Avatar
William Green

Michael, I am using Met/Team. I run all of my procedures from an approved projects folder which contains the PXEs. PXEs are executables. The PXEs are the only items stored in or linked to in Met/Team. I prefer using my projects folder(s) because I can store my documentation there as well. We maintain control of our procedures by limiting access to Met/Cal Editor. We can only run PXE's. All PXE's in our system are approved procedures. We asked Fluke to set it up that way. Does this answer your question?

Please sign in to leave a comment.