|
|
|
|
White Paper on Installing CDFs
Here's a PDF file on the proper procedures for registering/installing CDFs with your DFW applications. Written by Lawrence Fox of ComputerWizard Computing.
DataEase 6.0 is a 32bit program. As such, the supplied CDFs have all been re-compiled as 32bit functions. During this process, Sapphire made the supplied CDFs case sensitive, and left out a few items within the associated text/readme files. Graham Smith of PLM Consulting has resolved these problems in the above Zip file. When extracting the Zip file to your drive, be sure to check the use folder names box in the extract dialogue as the files are in subdirectory structure in the WinZip file. This sample 6.0 applet is supplied by Barry Peterson of Tampa, Florida as an example of TABBED screens. There is no username or password. Use the link to email Barry your thoughts or comments. Full Application DIW File Maker by Steve Woods This is a DFW DQL that produces a full-application DIW file (tables, documents, data, relationships, users, custom functions, etc.). Useful for rebuilding the full application in a new directory. Needed because over time, DFW's RDRR builds up many false tables that you can only eliminate by rebuilding the application from scratch. An example of the output is also attached (tinstall.diw).
Instant Install DFW_INST.ZIP This file is 198k. This app actually accompanies an article in the August 2000 issue of Dialogue, and just happens to also, IMHO, demonstrate the use of several CDF libraries -- CDFS2, DEMACRO, DFWACTS, MSGBOX and OSFUNC. You must read the accompanying literature -- not least of which, I took quite some time to write it! This is actually a real applet that I have built for my own development work to let me quickly create DIW files. It contains a lot of advanced techniques, most if not all of which I have trailed in Dialogue over the past years. Again, the accompanying documents -- one of which is the actual article from the last Dialogue -- give details. It is not offered as an 'alternative' to ClubParadease, nor does it have the approval of Sapphire for that function. It is not a beginner's app, but I hope you find it an interesting one<g>. The CDF libraries used and an import file (allcdfs.dat) are in the zip file. You point the app at the CDFs by making sure that the library name field in the custom functions table contains the path -- bear in mind that there is a 40-char limit to this field, I think, so the path has to be relatively short. Also, Dfw does not recognize long filenames, so you'll have to use 'progam~1', etc. Again, instructions on this are given. You can put the CDFs in the app directory or in a public folder; I can't see that it makes any difference, although I like Fred's recent point about having everything in one place. Feedback on this would be appreciated, of course. Cheers, Adrian BOR's CDF.Dat The DFW 5.5 "Demo" version is limited to a max of 50 records in any table. When "importing" Adrian's CDF file (ALLCDFS.DAT) that registers certain CDFs, it contained some 200+ records which did not "import" records beyond the 50 limit.A number of the CDFs Adrian requires for his app were in the "discarded" records. So, CDF problems solved in the following fashion: 1). Delete the 50 existing records and Reorganize the CDF Table. 2). Using Adrian's docs, rather than use Adrian's file (ALLCDFS.DAT). Use this BORCDFS.DAT. |