Just double-checking, Jim. You’ve verified that by using the Clarion Trace tool?
I ask because I do not have 11.1 installed.
My dev machine has the Native Client 11 and the ODBC client 17 installed.
Running your app compiled with C11.0, trace shows that the Native Client 11 is chosen by the Clarion driver and the app works without using SET.
Running your app compiled with 12, trace shows the ODBC 17 client is chosen and the app fails without using SET as you describe..
That sounds like what Z was suggesting…
Also… doing a quick scan of the ClaMSS.dll from both versions, it appears to me that the C12 version is aware of ODBC Driver variants, whereas the 11.0 DLL is not… which is confirmed by the debug behavior I see.
Window WINDOW('Caption'),AT(,,375,54),FONT('Segoe UI',10),GRAY
PROMPT('Entry Value:'),AT(7,7),USE(?wrkEntryValue:Prompt)
ENTRY(@s20),AT(58,7,91,10),USE(wrkEntryValue)
PROMPT('List Value:'),AT(7,21),USE(?wrkListValue:Prompt)
LIST,AT(58,21,91,10),USE(wrkListValue),DROP(2),FROM('One|Two|Three|Four|Five')
PROMPT('In CW12 this is transparent, but ealier versions not transparent'),AT(160,22),USE(?PROMPT1)
PROMPT('Entry Value:'),AT(7,37),USE(?wrkEntryValue2:Prompt)
ENTRY(@s20),AT(58,37,91,10),USE(wrkEntryValue2)
END
What you don’t mention is the runtime PROP changes to the Control Background Colors, that’s the problem. Also you make them FLAT. The change of TRN=False does not matter as the originals did not have TRN.
In my tests the FLAT did not matter. I would say the problem is that at runtime ?wrkListValue {PROP:Background} = COLOR:White is not changing a LIST to White, but it does work on the ENTRYs.
I can confirm that bug that ?LIST{PROP:Background}=### works in 11 and does not in 12. What does work is at design time adding COLOR(Color:White) to the LIST, but then you cannot change that color.
Here is my test procedure:
KevinsListColorTest PROCEDURE()
wrkEntryValue STRING(20)
wrkEntryValue2 STRING(20)
wrkListValue STRING(20)
wrkComboValue STRING(20)
wrkListFEQ LONG
Window1 WINDOW('Caption'),AT(,,375,54),SYSTEM,FONT('Segoe UI',10),COLOR(080FFFFH)
PROMPT('Entry Value:'),AT(7,7),USE(?wrkEntryValue:Prompt)
ENTRY(@s20),AT(58,7,91,10),USE(wrkEntryValue),FLAT
PROMPT('List Value:'),AT(7,21),USE(?wrkListValue:Prompt)
LIST,AT(58,21,91,10),USE(wrkListValue),FLAT,TIP('This should be White'),DROP(9),FROM('One|Tw' & |
'o|Three|Four|Five')
COMBO(@s24),AT(158,21,91,10),USE(wrkComboValue),FLAT,TIP('Combo'),DROP(9),FROM('One|Two|Thre' & |
'e|Four|Five')
PROMPT('Entry Value:'),AT(7,37),USE(?wrkEntryValue2:Prompt)
ENTRY(@s20),AT(58,37,91,10),USE(wrkEntryValue2),FLAT
END
CODE
open(Window1)
?wrkEntryValue{PROP:Background} =color:white
?wrkEntryValue2{PROP:Background}=color:white
?wrkListValue{PROP:Background} =color:white !<-- Does NOT work to change LIST Color !!!
?wrkComboValue{PROP:Background} =color:white !Combo works because its an ENTRY
wrkListFEQ = ?wrkListValue{PROP:ListFEQ}
! wrkListFEQ{PROP:Background} = COLOR:Orange !Changes Drop List color not List Entry
ACCEPT
END
Screen Capture of my test showing 12 does not set Background on LIST with DROP. In my tests without DROP it worked. Also FontColor worked.
My Apps compile and startup OK, but when ever I choose a menu option which STARTs a browse procedure (or any type of window) the program completely locks up. I have compiled with debug mode and put traces in the STARTed procedure but nothing is displayed. In the debugger i break on the start and then step and it locks up. No GPF or anything - just LOCKs up.
This all is fine in cw11x - I am just recompiling in CW12
surely this is good news as that from a forensics point of view it shows onesome has done some work on the runtime… which means someone somewhere is working on the product? good news…even if it means they broke something!!! We have evidence that some work is being done on the product!!!
Why can no one from SV or Marko ever respond? We have waited YEARS
for resizer and other updates. Marko said the updates were at SV and
for next release. Guess not.
This is so frustrating, there is so much potential with AS but it seems
to be a VERY LOW priority for SV. Frankly the potential of AS is the
hope that has kept me engaged, but the sun is about to set!
Brent Engel has brought this to us :
Marko, can you please clarify, is there an update to AS in the new C12
release? Is there a new server version? What exactly does the new C12 have
in it related to AnyScreen?
Yes, Anyscreen resizer and new build of Anyscreen is at Softvelocity on testing
phase for almost 2 years now. Robert Z is not responding on current ETA, so I
can only suggest to ping SV at this point. I guess development with C12 took
its tool, but I can’t do nothing about this from my side.
In 12 I have built the SQLite example that’s from the TPS School example. It START’s Browses from the frame fine. You might try an example on your system.
@Daniel1@ironmansculler and others, let’s please stay on topic here which is Problems found in Clarion 12. I want the Wizatrons back but that’s not a problem in 12.
“C:\Clarion11\LibSrc\win\TPLEQU.CLW”
Line 36: Warn:RIDeleteError EQUATE (17)
Its going to be a case of tracking it back.
Now one of the reasons why I like Notepad++ is it has a plugin called ComparePlus which lets you do side by side compares as you can see here, C11 ABError.clw on the left, C6 ABError.clw on the right. Changes get highlighted.
I would suggest the School TPS example. Modify the DCT to add a RESTRICT … I would think it might be there already for a file.
Then you should be able to compare that there’s a difference in the template generated CLWs or ABC class compared to 11. For Legacy the generated RI in the _RD.CLW.
Ok. tried School app. CLASSES tabled is linked to ENROLLMENT with a “RETRICT” on DELETE.
ABC
Compiled and it works in Clarion12. The prompt appears when trying to DELETE a record from the CLASSES table when a reference/link exists. As expected!
Hmm,
Back to my app.
Now Re-compiling in C12 and viola! Prompt appears to restrict the delete.
Forgive me all!
I will have to perhaps do some more testing. My gut feeling is that C12 DCT editor is perhaps “not” reflecting/exposing the RESTRICT “attribute”.
In CW12 my compile errors do not open in the Embed Editor like in CW11. Anyone else see this issue? - I am having a problem finding the setting to make sure it is set.
Tools, application options.
I think there are 2 settings there in play (on different tabs). The setting itself is the opposite - as i recall - if On, it goes to the CLW not the embeditor.
