>>>LOCAL oSQL AS sqlfunction of \libs\sqlfunction.prg
>
>
>But I declare oSql AS PUBLIC at my startup program. Does "LOCAL oSql AS sqlfunction ..." will cause conflict?
>
>
>At my startup main program
>
>.
>.
>.
>PUBLIC oSql
>oSQL = NEWOBJECT('sqlfunction','libs\sqlfunction.prg')
>.
>.
>
>Thanks

If you must keep your public variable, you can surround the alternate definition with IF .F./ENDIF or #IFDEF noexist/#ENDIF so it won't even compile into your code, but will be available for intellisense.