Hi all, I have written a two part series of exercises to introduce the Clarion FileManager and demonstrate how to use it, with some basic code examples. See Introducing Clarion FileManager (Part 1) and (Part 2) I would appreciate any feedback, comments, or bug/typo reports. I am planning to do ad…

I have updated both posts. Part 1 no longer mentions .init and .kill methods. Part 2 shows the use of SET(key) and SET(key,key) and all the code and screen shots have been updated accordingly. The code all works and has been tested in debug mode as well, but only with TPS files. I will do another po…

Looking at the below code it appeared odd to me to call .Init() / .Kill() for a File Manager. I’ve never done it and I am familiar with the code having written Init code to make ABC work with Legacy . Access:Customer.Init() <-- ??? Init ? Access:Customer.Open() i = 0 ! Record count…

Your example shows this code to read all the records in the Customer file in KeyCusNumber sequence: [image] The SET() statement has 7 ways to read a File, so it can be confusing. One (File,Key) should never used, it often ends up in code when GET(File,Key) changes to SET() without making it SET(K…

Thanks for the feedback, everyone. I agree that .Init and .Kill will cause problems when run from a FORM. I mentioned that in the article when doing an example of a button on the form. You only use this when using standalone code, which I was calling from the Menu, not a form which is already using…

[image] DonnEdwards: I agree that .Init() and .Kill() will cause problems when run from a FORM. … You only use this [ Init/Kill ] when using standalone code, which I was calling from the Menu, not a Form which is already using the table in question I would bet money you should Never call File…

Thanks Carl. I have modified the posts and added in an explanation. I hate it when the help file is misleading.

Donn, I skimmed part 2 where you showed using the “Try*” i/o methods. Maybe I missed it, but did you explain how the i/o methods without the “Try” prefix will display various fatal error messages on-screen and prompt for a response and perhaps even terminate the program? Were you planning on d…

I don’t have any experience with the Error class yet, but I realise it is best to look for errors and deal with them rather than confront the user a dreadful message that terminates the program. The blog article is only an introduction. Perhaps I can do another article later, once I can figure out …