Nevermind, .329 fixed it. Hard to keep up with all these updates : )
----- Original Message -----=20
Sent: Tuesday, February 29, 2000 1:56 PM
Subject: [Emerald] Strange Things with .328 in the Credit Card Fields
With Emerald 2.5.238 under the Windows 98 operating System
we are seeing very strange things when trying to change items
in the credit card fields.
If you replace a card holder name and swith to a different field
the name reverts back to the old name. This happens with the=20
card number and date as well.
Even though the displayed information switches back to the old info
you are trying to replace, when saved and reloaded the new information
is saved and displayed.
If you change autobill from 0 to 1 or vise-versa and save then the new
value for autobill replaces the card holders name instead.
All of this is very confusing to my billing people.
NOTE: This does NOT happen under the Windows NT operating
system, Everything works perfectly under NT
I have not tested with Windows 95, I dont not have any 95 =
PLEASE Help ASAP! I think this might have been happening with .327
also but not sure. I needed bug fixes that were in .327 and can not =
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
------=_NextPart_000_0006_01BF82BF.FA966D30------- Original Message -----From:=20 AdministratorSent: Tuesday, February 29, =2000 1:56=20 PMSubject: [Emerald] Strange =Things with=20 .328 in the Credit Card FieldsWith Emerald 2.5.238 under the =Windows 98=20 operating Systemwe are seeing very strange things =when trying to=20 change itemsin the credit card =fields.If you replace a card holder name and =swith to a=20 different fieldthe name reverts back to the old =name. This=20 happens with thecard number and date as =well.Even though the displayed information =switches=20 back to the old infoyou are trying to replace, when saved =and=20 reloaded the new informationis saved and displayed.If you change autobill from 0 to 1 or =vise-versa=20 and save then the newvalue for autobill replaces the card =holders name=20 instead.All of this is very confusing to my =billing=20 people.NOTE: This does NOT happen under the =Windows NT=20 operatingsystem, Everything works perfectly =under=20 NTI have not tested with Windows 95, I =dont not=20 have any 95 workstations.PLEASE Help ASAP! I think this =might have=20 been happening with .327also but not sure. I needed bug =fixes that=20 were in .327 and can not go backto .322John =Troher