Search results for query: *

Like a link script ;-) blinker output ... blinker inceremental off blinker executable extended blinker executable clipper f:55 file ... . . . lib signega lib ct . . .

You can use ADVANTAGE RDD

application is ranning properly in real mode. when I link it in extended mode the error ocures.

Hi everybody I have an application with clipper 5.2e which is linked by blinker 3.2. And I want to migrate to dos extended mode. beacaus of a peace of C code in my application that has became a problem for me. When I run the application an error happens when any of my C functions is be called...

In second point of my previous note I meant comment that to lines of your code. like this: // errorblock({ |obj| ERRORPROC(obj) }) and : //errorblock ( defblock ) ok?B-) now compile and link and run your program and see if the default error handling system reports any error. and tell me the...

1. I know you have supervisor rights. but what about the users of your application. CATools have a function for LOGIN. doesn't your application use that?. If yes with what login name? if there is such login name you must check it. 2. do a test. comment following two lines in your main menu...

1.are you using a unique login name when you run your application ? it's possibe you have restricted this login name to maximom two simultaneous workstation. 2. send your function source and it's subfunctions compeletely to me so I can give you an idea. Your problem is probobly in a networking...

bozz is right Leslie. your problem is in ERRORPROC() function. when you call errorblock(), the error recovery system is replaced by the codeblack that you pass to it. if the codeblock has errors it call itself. and that repeat in a infinite recursive process. you can send source of ERRORPROC()...