If you are one of the many companies who manage supplementary data outside your QAD system, you may want to consider adding this information to QAD to both keep it up-to-date and make it accessible to everyone who needs it. But, it can be time-consuming and expensive to do so.
In this 20-minute webinar we discuss available options and their pros and cons. Plus, you’ll learn about an easy, clever, and affordable option for maintaining supplemental data in QAD.
Where is the data kept? A separate table or a separate database?
A separate database is not required, nor is the revamping of the existing database structure. The QAD database contains a dedicated table in its structure called User Workfile (usrw_wkfl). It is part of the QADDB database, which is designated for storing anything QAD users may require for their own use. With the use of key fields, the User Workfile table can accommodate different datasets (or virtual tables). You define these tables and massively manage their records with the Extension Workbench.
Is there a limit of how much data you can load to the user workfile?
There is not a limit of how many records can be stored in the User Workfile. There is a limit to the number of fields you have for each dataset: 15 character fields, 15 decimal fields, 15 integer fields, 15 logical fields, 4 date fields. Some extra effort will be required to link and store your custom parent-child dataset structures, for example, contact header records and contract detail records. But if you do not mind storing such datasets in one level like we demonstrated the contracts in the webinar, then it’s very simple to do.
Did I understand correctly that the different user workfile fields can be validated against different QAD fields?
Yes, that is correct.
Can the User Workfile (usrw_wkfl) data be viewed inside QAD? Or do you always need to view via Excel?
You will use Extension Workbench to manage datasets records. To be able to fully benefit from integrating the supplemental data into QAD, you will need to embed this data into your QAD Reporting. Extension Workbench documentation explains how you can access datasets and the specific fields you need. Knowing that, your internal technical folks [or any QAD technical consultants] should be able to adjust your reporting and creating new .NET UI browses. Alternatively, we will be happy to help you.
Any issues for EE vs. SE?
No issues. The product works well with both QAD SE and QAD EE versions.
What is ICT?
ICT (Integrated Customization Toolkit) is a QAD product which is designed to enable user defined logic in maintenance programs. For example, with ICT, your Item Master maintenance program can bring a new frame with new fields in it.
I heard ICT is being phased out by QAD … is that correct?
ICT is in use by some of our customers. We have heard about issues these customers experience with ICT, but we haven’t heard that it is being phased out.
Join our mailing list to stay informed about our webinars
