SQL ERROR

Phil (OmnisList) phil at pgpotter.co.uk
Fri Feb 12 09:12:29 UTC 2021


Like you Das,

I see
instance error: SQL DAM not supported

and wonder if you have the correct omnis licence?

Because the code otherwise looks OK.

regards
Phil Potter
Based in Chester in the UK.

On 11/02/2021 22:33, Das Goravani wrote:
> On second thought getting as far as you have with Postgres I guess it’s clear you’re licensed for it. Re reading the thread I got nothing to help you with. The obvious: Is there a way to do what you want without that command? I never use it, but I’m very basic.
>
> Your way of using a local variable to hold a list that is displayed is questionable. Normally anything on the form is in a variable from the form, like an instance variable, I forget what names the form variables have, but you want to use the next kick up from local, give yourself some global ability with it, A local variable is meant to be used only in code in that one method.. a very temporal passing designation.. not meant for display per se, I noticed another funny placement or usage of something..
>
> also note, it’s hard to read your original post as the lines all run together.. do what you can to make it not like that.
>
> On first read it sounds like the Omnis DAM and the Postscript DAM both do not support that command.. that’s how it reads.. adding your comments together.. I dont know what SQLText contains.. and I dont feel like looking it up, but it sounds like it holds your previously defined SQL statement text.. hold it in something of your own and bypass that command.. that’s what I’d do anyways
>
>> On Feb 11, 2021, at 2:07 PM, Das's <goravanis at gmail.com> wrote:
>>
>>
>> Martin,
>>
>> Just off the top of my head I wonder if that is a message from a different place, namely the licensing department, you have to buy your way into SQL with Omnis.. then you get a different license number.. which supports the DAM.. just wondering I guess if your licensed for it all.. I’m guessing you are and that message therefore likely comes from that command not being supported.. unsure I thought I’d post it
>>
>> Das
>>
>>> On Feb 11, 2021, at 12:33 PM, Martin Obongita via omnisdev-en <omnisdev-en at lists.omnis-dev.com> wrote:
>>>
>>> Andy,
>>> I have changed the task object sub type to PGSQLSESS so as to use a Postgres DAM.It successfully connect to the database.But I still get the error "DAM not supported" when I execute the statement $sqltext.
>>> Regards,Martin.
>>>
>>>    On Thursday, February 11, 2021, 10:46:50 PM GMT+3, Andy Hilton <andyh at totallybrilliant.com> wrote:
>>>
>>> Ok on second reading it suggests that the Omnis SQL DAM does not support $sqltextinstance……which sounds highly likely - I was never ever fond of the Omnis SQL DAM, way better to use real sql in my opinion !!
>>>
>>> Andy Hilton
>>> Totally Brilliant Software Inc
>>> Phone (US) : (863) 409 4870
>>> Phone (UK) : 0207 193 8582
>>> Web : www.totallybrilliant.com <http://www.totallybrilliant.com/>
>>> Helpdesk : http://totallybrilliant.kayako.com
>>> Email : andyh at totallybrilliant.com
>>>
>>>> On Feb 11, 2021, at 2:32 PM, Martin Obongita via omnisdev-en <omnisdev-en at lists.omnis-dev.com> wrote:
>>>>
>>>> Thanks Andy.The customer list is a local variable to that method only, for the purpose of displaying data in the current remote form.I would guess that since the customer table is a sub type of the lvCustomerList, it would call the sql error method in the super class when the $fetch command is executed since the table tSuper is a super class of the customer table class.
>>>> Regards,Martin.
>>>>     On Thursday, February 11, 2021, 10:21:33 PM GMT+3, Andy Hilton <andyh at totallybrilliant.com <mailto:andyh at totallybrilliant.com>> wrote:
>>>>
>>>> Martin
>>>>
>>>> A wild ass guess but did you define your variable as a local variable (convention would say naming it ‘lvxxxxx’ would indicate a local variable) and are trying to reference it in a different method ? ‘Local’ variables are only alive within the scope of that one method, if that is the case change it to an Instance variable to widen its scope (you can drag from local variables list in to the instance variables list)
>>>>
>>>> Andy Hilton
>>>> Totally Brilliant Software Inc
>>>> Phone (US) : (863) 409 4870
>>>> Phone (UK) : 0207 193 8582
>>>> Web : www.totallybrilliant.com <http://www.totallybrilliant.com/> <http://www.totallybrilliant.com/ <http://www.totallybrilliant.com/>>
>>>> Helpdesk : http://totallybrilliant.kayako.com
>>>> Email : andyh at totallybrilliant.com
>>>>
>>>>> On Feb 11, 2021, at 2:13 PM, Martin Obongita via omnisdev-en <omnisdev-en at lists.omnis-dev.com> wrote:
>>>>>
>>>>> Hi $all,
>>>>> I have successfully logged on to an omnis database using OMSQLDAM
>>>>> I have a remote form with a button "load" which I use to select and fetch data.In the $event method, I have defined a variable:lvCustomerList variable of type tCustomers
>>>>> "tCustomer" table class "tSuper" super class
>>>>> In the "tSuper" table class I have defined a variable:lvStatementObjRef Variable of Type Item Reference
>>>>> In the class method "$sqlerror" I have the following statement:Set reference lvStatementObjRef to $cinst.$statementobjectCalculate iScript as lvStatementObjRef.$sqltextCalculate iErrotText as lvStatementObjRef.$nativeerrortext
>>>>> When I execute the load method, I get the error below:e125207 Problem with notation unnamed_value.$sqltextinstance error: SQL DAM not supported
>>>>> Any assistance is highly appreciated.
>>>>> Martin.
>>>>>


More information about the omnisdev-en mailing list