ABC: Using FileManager methods in source procedures 1998-12-15 -- Barky@lansharks.com (keith Barkenhagen) Newsgroups: topspeed.products.c5ee Well, just thought I would post a follow up to my first message detailing what worked and what didn't. Using the Generate All checkbox in the global properties didn't work. Using the individual file overrides didn't work either. What DID work was to create a browse in my app. Even though I didn't export it, and never used it, it would appear that the instantiation of the FileClass doesn't happen without a browse there. This is a borderline bug, because if I am using the dictionary, and I add the file into the OTHER FILES area of my source procedure I should be able to access the file objects there. So, IF you have only a source procedure (ie: you're creating a DLL that has only source procedures) that needs access to the files and you are going to be programming using ABC Methods, you HAVE to create a browse to that the file objects are created. This might be a good entry into some of the tip databases out there... I don't know how to go about getting it into those databases, but here it is to the newsgroup community. Best of Luck and Happy coding, Keith Barkenhagen >I would like to use ABC-type calling methods in a source procedure to >access a file. In other words, I would like to be able to call >Relate:SysLog.PrimeAutoInc() so that the Clarion will automatically >autoinc my file for me. > >My problem is I can't seem to get my source procedure to recognize ABC >methods at all... I can Open(SysLog) fine, but I am NOT able to >Relate:SysLog.Init or Relate:SysLog.Open(). How can I get this to >happen? I keep thinking that there must be some easy way to include >the relation manager into a source procedure. > >The error that is spit out when trying to use ABC methods is: "No >Matching prototype available" Printed November 21, 2024, 11:47 am This article has been viewed/printed 35376 times. Google search has resulted in 29 hits on this article since January 25, 2004. |