1. Andres Slachevsky
  2. PowerServer 2020 or older (Obsolete)
  3. Wednesday, 5 September 2018 18:12 PM UTC

Using MS SQL SERVER
if in the SQL of the Datawindow there is a comment then when the retrieve() will not work and no error dysplay

will be great if in the log after the deploy of the application is a warning

 

Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Thursday, 6 September 2018 00:25 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Andres,

This issue should be caused by the single-line comment symbol '//', PowerServer only support multi-lines comment symbol '/*…*/' in datawindow, and PowerServer does not support char ':' in comment, please solve this issue by using multi-lines comment symbol '/*…*/'.

Regards,
ZhaoKai

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 5 September 2018 18:51 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Andres;

   Please open a Support Ticket on this issue.

   FWIW: A workaround could be to parse out the DML comments in the DC/DS's RetrieveStart, SQLPreview or right after the DWObject's load (ie: Post Constructor) event before PowerServer processes the current SQL and replace it with a cleaned-up copy of the DML statement. Hopefully, you have a common DC/DS ancestor where you can implement this code. Replacing the DML would only be "in memory" so the DWO source would not be affected.

   Note that you would only have to run the SQL clean-up code logic when running under PS as a Web or Mobile App. So you could check the Client Type in the "appeonextfuncs" object located in the Appeon_Workarounds library for that (method: of_getclienttype).

HTH

Regards ... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.