Aparajita,
I think we are all agreed that unicode mode is best....but I am
intrigued as to why you asked the question initially.
Is there an advantage to you if Active4D doesn't have to support
compatibility mode? Will it save you some development time/testing?
If yes I for one would be happy with no compatibility mode (at least
in the first release) - that way we all benefit from having A4D v11
sooner.
M.
On 15 Sep 2009, at 20:55, Aparajita Fishman wrote:
Please note that Active4D v11 is ALWAYS in Unicode mode. You may
not be able to access 4D process or interprocess text/string
variables in Active4D if the database is in non-Unicode mode. I
haven't tested this yet.
I have tested this now, and it's much better than I thought it would
be:
In Unicode mode there are no restrictions on process/interprocess
variable usage.
In non-Unicode mode:
- Text variables/arrays are read write.
- String variables/arrays appear to Active4D as text variables/arrays.
- If you declare a process/interprocess string variable/array in 4D,
it is read only.
- If you declare a process/interprocess string variable/array in
Active4D, it is read write.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoy.org
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
