Given the issues regarding LotusScript code compiled in 32 bit versions can cause errors for 64 bit clients and vice versa what would people recommend as a migration process?
As we have multiple clients across multiple sites we can't do a "big bang" and migrate all at once.
If you migrate at a slow pace then we will hit the issue as some 64 bit clients will be executing 32 bit code.
If we compile all code to 64 bit first then there will be issues of 32 bit clients executing 64 bit code.
Update 29 Jan 8:32 GMT
I am interested to know if there are any upgrade processes, recommended by HCL, or other users, to best avoid issues in a mixed 32/64 bit environment.
e.g.
1) Upgrade designer clients to latest 12.0.2 FP5 32 bit
2) Recompile all code in all DBs.
3) End user Notes 64 bit roll out
4) Upgrade designer clients.
some reported issues in mixed 32/64 bit environments
LotusScript code compiled on 32bit client fails on 64bit client, and vice versa. Not fixed until 14.5
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0105456
LotusScript NotesView.GetAllEntriesByKey issues
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0102291
LotusScript Arrays - "out of stack space" error due to more memory allocation in 64 bit but still 32K overall limit.
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0040725
LotusScript - array of long values bug in 64 bit
https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0101520
LotusScript Replace() - Passing an Array to replace function returns an empty string to older Notes version when a LotusScript is compiled using Domino Designer 12.0.2 FP2 64-bit