Looks like you could use <@SERVERNAME> and configure the .ini file so it reflect the different servers.
You could either maintain two code sets with encoding or maybe create a custom scope that you use for encoding based on the servername returned.
Seems like a possible interim solution.
on 11/7/04 12:47, Chuck Lockwood at [EMAIL PROTECTED] wrote:
Is there a way to keep a application compatible with both 5.0 and 5.5 encoding methods? I am in the process of porting a fairly large application over to 5.5, however I am still developing and deploying in 5.0, trying to meet a development deadline. In other words, I can not just abandon 5.0 for 5.5 in one fell swoop!
Is there a server setting, such as OldEncoding = true or some other method of working with the same application on both versions simultaneously? Is this possible?
Chuck Lockwood
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
LockData Technologies, Inc.
309 Main Avenue, Hawley, Pa 18428
570-226-7340 ~ Fax: 570-226-7341
[EMAIL PROTECTED] ~ www.lockdata.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
--
Dan Stein
Digital Software Solutions
799 Evergreen Circle
Telford PA 18969
Land: 215-799-0192
Cell: 610-256-2843
Fax 413-410-9682
FMP, WiTango, EDI,SQL 2000
[EMAIL PROTECTED]
www.dss-db.com
"When you are born, you cry and those who love you rejoice. And if you
live your life as you should, when you die, you rejoice and those who
love you cry."
________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
