Thursday, February 24, 2005
Tell Me about Reinitializing a TLC DATAFILE
Running the undocumented utility called REINIT.EXE can be dangerous. You can find it on the CD-ROM that came with your
system (look in the :\TLC32(Prof or ORG)\EXTRAS\ Directory). It will reinitialize a database's TLC files to zero length files.
To run this utility it must be run from Command Line. Be sure your TLCDATA environment variable is SET to the correct
directory before running this utility.
The following is an example about how to do this.
First, Change Directory to where the ReINIT utility is and set the TLCDATABase environment variable.
C:\TLC32\Bin>set tlcdata=c:\tlc32\gentexd (this is the same as the TLC.CFG setting)
Now you can run the command - a sample session is shown below the command
C:\TLC32\Bin>reinit
The 'c:\tlc32\gentexd/toolid' file contains 2036 records.
Do you wish to erase and reinitialize the file? n
The 'c:\tlc32\gentexd/kitid' file contains 0 records.
Do you wish to erase and reinitialize the file? n
The 'c:\tlc32\gentexd/kitdef' file contains 0 records.
Do you wish to erase and reinitialize the file? y
Are you sure?
As you can see it will ask you twice if you answer Yes to any reinitialization.
Note: Cntrl C will get you out of the utility and EXIT at the C: Prompt will get you out of Command Line.
Running this utility will create empty database files or you can simply copy the empty database files from the TLC32 CD-ROM.
Example to create an empty KITID.DAT, KITID.IDX and KITID.LCK file, copy the files of the same name from the CDROM Directory:
\TLC32(Prof or ORG)\EXTRAS\data.
The file sizes should be: KITID.DAT -0KB, KITID.IDX -3KB and KITID.LCK -1KB. You cannot create an empty CISAM file unless
you use the REINIT utility.
Copying from the CD is the safest way.
Remember to change the properties of the
files to ARCHIVE after you copy them from the CD to your DATA directory.
If you are working on one database you may want to have it copied or backed up before running this utility or replacing files.
If you are creating another database you may want to copy or rename an existing database and REINIT it. In the end the data
in the data files of the database you REINIT will be destroyed.
9:02 pm
Saturday, November 13, 2004
KIT & Assembly CONTROL Questions
- Kit Returns - When returning kits, can they be returned in "pieces", or do they need to be returned as a complete/whole
unit?
- Answer - YES to both.
- If you are using Economy Level TLC K, and a kit is returned manually by its individual pieces, each piece may be returned
to storage, scrapped or sent to rework. If more items replacements were independently (individually) issued to the floor to
resupply this kit, they will also be returned. For instance, if 10 inserts were issued with a face mill and then 10 more were
later issued to replace the worn inserts, all twenty could be returned with the kit.
- If you are using TLC32 or Legacy Organizer (2.7.2), you can return the kit components in an automatic mode so you do not
have to individually select the tools to return.
- If you are using TLC32 or Legacy Professional (2.7.2), you can define Kits as tool assemblies and further complicate the
return by breaking kits down and breaking tool assemblies down. For more information, I would suggest some in-plant training
or attending one of the ITC classes this year. You can also refer to the Advanced Kitting section of your TLC Manual.
8:03 pm
Common Questions -Auxiliary Tool Code Searches & Reporting Tool Use
Auxiliary Search Sort Misunderstanding - A user complained that the Aux. Tool Search does not sort the tool numbers
in any understandable order.
- Answer - The problem was caused because the tools had no Auxiliary Identification or Dimension 1 and 2 fields filled in.
The user wanted an update to the sort sequence for Aux. Code search and the Aux. Report. The Auxiliary sort sequence has *ALWAYS*
consisted of THREE parts: AUX. ID, Dim1, and Dim2. In order to change this it would take adding a new index to the toolid
file as well as additional code on all functions that use the AUX. Code. A practical solution is to use the Aux. Code as intended
originally by the TLC software. We would suggest adding SOME dimensions to the tool AUX Code definition. If this is not the
easiest solution, then you can write a special report with TLC ReportWriter (Option Add-On for special Reports.
ITEM ACTIVITY REPORTING.
ATMS provides extended capabilities regarding usage periods and allows the customer to define his own specific usage periods.
Another user asks - Can I generate a report showing me which tools were checked out the most? For instance, how many times
a toolholder has been on the floor for the year. Can this be done? If so, how?
-Answer -The standard (IA) Item Activity Report will give you the tools' Description its Perishable-Durable Returnable-Non
Returnable status, Availability, Reorder point, Usage (quantity issued) by MTD-YTD-LM-LY, Last Used Date, Unit Cost and the
Aux. Code.
- Where do I need to go in order to do this? - It is available on the Reports Menu screen as the Item Activity (IA) Command.
You must reset your usage counts every month and every year in order for this report to do its job properly. Resetting the
Monthly counts will zero the issues for this month (MTD) and move that count to LM - (Last Month). Resetting the Yearly count
(YTD) will zero the count for this year and move the count to LY (Last Year). This is done from the Supervisors Menu through
the (RU) Reset Usage Command.
7:57 pm
Concerns about upgrading to TLC32
. What ITC product would be the least trouble to switch my current database over?
Answer -Any TLC32 product. If you are currently using the TLC Legacy version. Upgrading to TLC32 will also bring you up to
Revision Level 2.7.2 and add New Command Screens to the look and feel. TLC32 will operate the same as your Legacy version
while adding new screen controls.
2. Will it be multi-user?
Answer - YES. It will provide the same number of users you have now.
3. What is involved in moving the tool database? P.S. Detailed Explanations are in previous Blogs posted to this site.
Answer - First, error check all your tool database files with the TLCFIX or FILEFIX utility on your system. If you have no
errors, pick the FILEDUMP utility and dump each file in the database to a TXT file. For example, dump the toolid.IDX &
.DAT file to a file named TOOLIDS.TXT. Move those (.TXT) files to your Windows network and use the FILELOAD Utility in your
new TLC32 software to load the tool database. You will have all the information from your Legacy system now available in the
TLC32 system
4. What is the upgrade cost for the TLC32 product.
Answer - Depending on TLC32 product -$210 to $750 plus $30 to $150 per additional users. You might want to consider unlimited
users or a site license - $450 to $1800 for current customers.
5. Before we upgrade is there a trial version we can test with?
Answer - YES. To test against your current working tool database you must complete the conversion as explained in ANSWER 3
above.
Any TLC Legacy tool management product can be upgraded to the new TLC32 version. The TLC Legacy database will easily upgrade
to TLC32 database format.
If you are contemplating trading your TLC Legacy or TLC32 product in for an ATMS product, your database can be converted to
the ATMS format, however it must currently be done by ITC.
7:45 pm
Re-Ordering Tools with TLC32
· Reordering
The question has been asked - What file is being looked at for an order to be generated? Answer - none.
TLC does not generate an order. You do, using the Tool Order (TO) Command on the Supervisors Screen or Menu. Using the (TO)
command creates a record notifying TLC that the tool is now ordered. These ordered tools appear on the On-Order Report.
As you issue tools from the tool crib the quantity eventually go below the minimum quantity level you established when you
created the Tool Identification Record. This will trigger notification at the crib that you are below minimum quantity and
the tool will appear on the Supervisores Re-Order Report. Running a ReOrder Report can generates a list of these tools. These
tools are also made available on-screen for your approval during the Tool Order session.
Using TLC32 or Toolware32Deluxe to order your tools has several advantages.
1. Reorders are computed based on the type of tool. Example: Perishable tools, if the on hand quantity in the tool crib storage
cabinet are below the reorder point. Durable tools, if the quantity on hand, in storage, and in use on the shop floor are
below the reorder point.
2. Reorder computations can be modified to take into account inventories at machine cell storage locations or in Automatic
Tool Dispenser’s (ATD’s).
3. Nothing is established (or sent) as on order until you approve it.
4. You can update price, vendor, delivery date, and quantity to order on every order and choose to make it a standard or a
one-time-buy decision.
5. You can order tools that are not established in your tool database, including spot buys, or a new engineered tool.
You don’t have to send direct to the vendors; you can send to your in-house host for further order control and purchasing
department approval.
7:10 pm