[SOLVED]SQL BUILDER not working

Scriptcase 7 Bugs
#1

I created simple LEFT join on 2 tables. The first one has about 3000 records (MySQL)

PROBLEMS:

  1. When I RUN query it says no records can be found (?)
  2. When I save it and want to run the saved version again it pops me back to the query list and doesn’t even show any error
  3. CONFIRM button doesn’t work as expected ! (the HELP says: "When confirming it, SQL Builder moves automatically to the next step : Execution folder or Saved folder. ")

below is a SC ganarated query:

SELECT
  dDIESASES.DiseaseID,
  dBODYSYSATK.ID,
  dBODYSYSATK.DiseaseId,
  dBODYSYSATK.BodySystem,
  dBODYSYSATK.lang,
  dBODYSYSATK.OperatorID,
  dDIESASES.ComonName,
  dDIESASES.ComonSubname,
  dDIESASES.MedicalName,
  dDIESASES.LatinName,
  dDIESASES.OtherName,
  dDIESASES.Description,
  dDIESASES.Falg,
  dDIESASES.Locked,
  dDIESASES.lang,
  dDIESASES.Operator,
  dIMAGES.ID,
  dIMAGES.DiseaseId,
  dIMAGES.ImageName,
  dIMAGES.dImagePath,
  dIMAGES.lang,
  dIMAGES.OperatorID,
  dLINKS.ID,
  dLINKS.DiseaseId,
  dLINKS.LinkName,
  dLINKS.LinkURL,
  dLINKS.LinkDescription,
  dLINKS.Ranking,
  dLINKS.Editable,
  dLINKS.lang,
  dLINKS.OperatorID,
  dSYMPTOMS.ID,
  dSYMPTOMS.DiseaseId,
  dSYMPTOMS.Symptom,
  dSYMPTOMS.lang,
  dSYMPTOMS.OperatorID,
  dAUDIO.ID,
  dAUDIO.DiseaseId,
  dAUDIO.AudioTitle,
  dAUDIO.FilePath,
  dAUDIO.URL,
  dAUDIO.Ranking,
  dAUDIO.LinkNumber,
  dAUDIO.AudioDescription,
  dAUDIO.Editable,
  dAUDIO.lang,
  dAUDIO.Operator,
  dBODYPARTSATK.ID,
  dBODYPARTSATK.DiseaseId,
  dBODYPARTSATK.BodyPart,
  dBODYPARTSATK.lang,
  dBODYPARTSATK.OperatorID,
  dHOMEOTHER.ID,
  dHOMEOTHER.DiseaseId,
  dHOMEOTHER.ItemCode,
  dHOMEOTHER.HomeopathyItem,
  dHOMEOTHER.ProductPicturePath,
  dHOMEOTHER.ItemNotes,
  dHOMEOTHER.Editable,
  dHOMEOTHER.lang,
  dHOMEOTHER.OperatorID,
  dKEYWORDS.ID,
  dKEYWORDS.DiseaseId,
  dKEYWORDS.KeywordNumber,
  dKEYWORDS.ShortKeywordText,
  dKEYWORDS.LongKeywordText,
  dKEYWORDS.Editable,
  dKEYWORDS.lang,
  dKEYWORDS.OperatorID,
  dMEDICALPROC.ID,
  dMEDICALPROC.DiseaseId,
  dMEDICALPROC.ProcedureID,
  dMEDICALPROC.lang,
  dMEDICALPROC.OperatorID,
  dNUTRENTS.ID,
  dNUTRENTS.DiseaseId,
  dNUTRENTS.NutrientNumber,
  dNUTRENTS.NutrientName,
  dNUTRENTS.NutrientRDA,
  dNUTRENTS.NutrientPicturePath,
  dNUTRENTS.Editable,
  dNUTRENTS.lang,
  dNUTRENTS.OperatorID,
  dORGANSATK.ID,
  dORGANSATK.DiseaseId,
  dORGANSATK.BodyOrgan,
  dORGANSATK.lang,
  dORGANSATK.OperatorID,
  dPREVENTION.ID,
  dPREVENTION.DiseaseId,
  dPREVENTION.ItemCode,
  dPREVENTION.PreventionItem,
  dPREVENTION.ItemDescription,
  dPREVENTION.Editable,
  dPREVENTION.lang,
  dPREVENTION.OperatorID,
  dRECIPES.ID,
  dRECIPES.DiseaseId,
  dRECIPES.RecipeName,
  dRECIPES.DosageUnit,
  dRECIPES.MinimumDosage,
  dRECIPES.RecomendedDosage,
  dRECIPES.MaximumDosage,
  dRECIPES.NutrientRDA,
  dRECIPES.Matching,
  dRECIPES.Sidefects,
  dRECIPES.ChildrenUnder7,
  dRECIPES.Infants,
  dRECIPES.Pragnancy,
  dRECIPES.UseWithOtherMedicine,
  dRECIPES.OtherSugestions,
  dRECIPES.Editable,
  dRECIPES.lang,
  dRECIPES.OperatorID,
  dVIDEO.ID,
  dVIDEO.DiseaseId,
  dVIDEO.VideoTitle,
  dVIDEO.FilePath,
  dVIDEO.FileSize,
  dVIDEO.WebLocation,
  dVIDEO.Ranking,
  dVIDEO.VideoDescription,
  dVIDEO.Editable,
  dVIDEO.lang,
  dVIDEO.OperatorID
FROM
  dBODYPARTSATK,
  dORGANSATK,
  dBODYSYSATK,
  dKEYWORDS,
  dLINKS,
  dHOMEOTHER,
  dPREVENTION,
  dNUTRENTS,
  dRECIPES,
  dMEDICALPROC,
  dIMAGES,
  dAUDIO,
  dVIDEO,
  dDIESASES LEFT OUTER JOIN dSYMPTOMS ON dDIESASES.DiseaseID = dSYMPTOMS.DiseaseId
ORDER BY
  dDIESASES.ComonName

==========================================================

I discovered that when I ass several tables to the query on the TABLES Tab, all query statement gets screwed up…
The only way to get the right code is to do ONE TABLE AT A TIME, which sucks.

At some point without any reason just by going among the Tabs - I have lost all JOIN settings and had to go back and start over from scratch.

I just have discovered even worse bug! When I created and saved a SQL query, then later try to run it it simply DOES NOTHING, bringing me back to the SAVED QUERIES list. This is the code which previously worked. Has anybody tested SQL builder before releasing it? It seems like in this condition it is almost useless.

When I switch between the Tabs (after opening existing-saved query) I loose the SQL code, which is nonsense…

I created an SQL script from CodeChargeStudio, which generates valid recordset, and I can see the records in a data browser window. Then I pasted this same SQL script into SC SQL Builder and it doesn’t run at all !!!

Also - the option to REOPEN saved query for changes (through the wizard) is a MUST!

Arthur

#2

SQL BUILDER not working

SQL Builder is a total crap! It looses the settings, saved queries don’t run, no way to go back and edit existing query through the wizard.
Please fix the bugs !

Arthur

#3

Re: SQL BUILDER not working

Hello,

When working with large queries, I recommend you to use views instead of running the whole query.

I have reported this issue to our bugs team for further testing.

regards,
Bernhard Bernsmann

#4

Re: SQL BUILDER not working

OK, I hope this will be fixed soon. So far many bugs that were reported have not been fixed for months.

Where can I find some help on how to use VIEWS ?
Can I create VIEW using SC or need to handcode it ?

Arthur

#5

Re: SQL BUILDER not working

Hello,

I recommend you to create views on your RDBMS. What DB are you working with?

Article on views: http://www.w3schools.com/sql/sql_view.asp

regards,
Bernhard Bernsmann