pmo:
After upgrading to RC1, my servoy developer does not recoginize my database server connections anymore…
Here’s what’s in the “Problems” tab in developer:
Is anyone having this problem? thanks
it cant open the table editor for a table because your database server is disabled or invalid.
What happens if you just open the server itself? Is there something wrong with your connection?
Since this release I see 58 warnings as follows on the problems tab:
RowBGColorCalculation of form ‘BasLog’ is linked to an entity that doesn’t exist. BasLog.frm /HadesBasics/forms HadesBasics/forms/BasLog.frm Form Problem
The row bg color calculation is linked to a global method. This is a rather new possibility. Why do we get warnings now?
Regards
birgit:
Since this release I see 58 warnings as follows on the problems tab:RowBGColorCalculation of form ‘BasLog’ is linked to an entity that doesn’t exist. BasLog.frm /HadesBasics/forms HadesBasics/forms/BasLog.frm Form Problem
The row bg color calculation is linked to a global method. This is a rather new possibility. Why do we get warnings now?
Regards
I noticed the same problem. You can fix this by changing in 4.1 your RowBGColorCalc put it first on -none-, save your change and then change it back to the correct method and save it again.
Then export your 4.1 solution and import it again into 5.1. In my case that solved this warning
birgit:
Since this release I see 58 warnings as follows on the problems tab:RowBGColorCalculation of form ‘BasLog’ is linked to an entity that doesn’t exist. BasLog.frm /HadesBasics/forms HadesBasics/forms/BasLog.frm Form Problem
The row bg color calculation is linked to a global method. This is a rather new possibility. Why do we get warnings now?
Regards
What happens if you clean the projects (Project → Clean…) ? Do the markers reappear ? What if you restart developer then clean ?
They reappear.
Next tableview problem :
When navigating in tableview (Smartclient) beyond the 200 record limit with the PgDn key the complete foundset will be loaded !!
When I navigate (not too quickly !) with the down arrow key beyond the 200 record limit the next 200 will be loaded (as it should).
Are we paying the price for the new foundset multi select option ?
lwjwillemsen:
Next tableview problem :When navigating in tableview (Smartclient) beyond the 200 record limit with the PgDn key the complete foundset will be loaded !!
Great I want a functionality to load a complete foundset > 200 records
martinh:
lwjwillemsen:
Next tableview problem :When navigating in tableview (Smartclient) beyond the 200 record limit with the PgDn key the complete foundset will be loaded !!
Great I want a functionality to load a complete foundset > 200 records
![:lol:]( "Laughing")
![:lol:]( "Laughing")
Hi Martin ,
I think no when you have 450000 records in the table (as in our case) !
Regards,
martinh:
lwjwillemsen:
Next tableview problem :When navigating in tableview (Smartclient) beyond the 200 record limit with the PgDn key the complete foundset will be loaded !!
Great I want a functionality to load a complete foundset > 200 records
![:lol:]( "Laughing")
![:lol:]( "Laughing")
i am really really sorry then, because i fixed this behavior…
jcompagner:
martinh:
lwjwillemsen:
Next tableview problem :When navigating in tableview (Smartclient) beyond the 200 record limit with the PgDn key the complete foundset will be loaded !!
Great I want a functionality to load a complete foundset > 200 records
![:lol:]( "Laughing")
![:lol:]( "Laughing")
i am really really sorry then, because i fixed this behavior…
Hi Johan,
I see above fix not present in RC2.
In RC3 ? And if yes, when will rc3 be available ?
Reagrds
lwjwillemsen:
jcompagner:
ahh ok, so thats when you set the foundset
Thats an easier fix.Ok, but beware : at the moment of the form.foundset.loadrecords() that form is not (yet) shown…
Feel free to fix all of the easier fixes…
Hi Johan,
After testing in RC2 : not fixed in RC2.
As a workaround I issue an extra (dummy) setSelectedIndex(1) followed by setSelectedIndex(selectedIndexBeforeFormShow) after the tableview form is shown…
Then it works ok but I hope it will be fixed soon
I repeat my bug description : At show event the currently form.foundset.selectedIndex is not (always) in the tableview (screen) window !
Status ?
thats right it will be in the next build
RC2 build was already build.
jcompagner:
thats right it will be in the next build
RC2 build was already build.
Hi Johan,
I posted two different tableview issues noticed in RC1 where you commented on.
Can you please quote on the two one by one regarding RC2 ?
Thanks in advance…
After upgrading to RC1, all my database connections are gone.
i tried openning the local servoy admin page, and there’s no database connections.
But all the *.dbi files are still in my workspace’s local resources folders.
anyone else having this problem?
thanks
the database connections are specified in the servoy.properties file in your application server dir.
What does that file say?
thank you very much.
I re-created my servoy5 directory, and did not copy over the servoy.properties file.
so can I use the servoy.properties file from a servoy 4 installation on a servoy 5 install?
I just want to make sure this is safe to do.
thanks
yes you can
jcompagner:
yes you can
Hey!! There’s a trademark on “Yes you can”!
Since this release I see 58 warnings as follows on the problems tab:
RowBGColorCalculation of form ‘BasLog’ is linked to an entity that doesn’t exist. BasLog.frm /HadesBasics/forms HadesBasics/forms/BasLog.frm Form Problem
The row bg color calculation is linked to a global method. This is a rather new possibility. Why do we get warnings now?
Is there a solution for this issue ??
It is not possible for us to go back to 4.1 and then up again to 5.1.
It seems to be an issue with solutions that where upgraded from 4.1 and had global rowbgcalculations.
We get about 80 of these warnings in 5.1
Regards
Hi,
found a way to repair this :
set all rowbgcalcs tot none in forms properties
export modules/solutions
delete modules/solutions
import modules/solutions
I think it has something to do with de entries I see in the project exporer window.
for tables that had problems there was no pair of
Is this a Bug ?? It is not possible to reproduce it.
Regards,