Copy and Paste Problem in New Era Screen Superfields with regard
Posted in 1998
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------ =_NextPart_001_01BDA123.3EF09B48 Content-Type: text/plain; charset="iso-8859-1" We have noticed that there is a problem with the copy and paste function in superfields and shift policies of super fields. If you copy the data in a superfield that has an 'UPSHIFT' policy and paste it into a superfield that has 'downshift' or 'noshift' policies it will appear the correct shift policy until you focus out of the field. Then it turns to the shift policy of the copied text. This is a problem for us because when a user enters query criteria in the field where the data was pasted, they get no records found. This is because the shift policy of a given field is upper and the cut and paste function allows mixed case to be entered and saved into the table. Query criteria is entered in the field in whatever case the shift policy sets. To the user, this data doesn't exist since they cannot get to it. Has anyone come across this or have any ideas for solutions. I'm thinking maybe programming the 'focus out' event of the superfield to change the case of the data to the policy, but don't know how to do that. Thanks in advance, Kathy Hildebrand kathy@htscm.com <mailto:kathy@htscm.com> :-) Designer/Programmer ------ =_NextPart_001_01BDA123.3EF09B48 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.1960.3"> <TITLE>Copy and Paste Problem in New Era Screen Superfields with regard = to shift policies</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2 FACE=3D"Arial">We have noticed that there is a = problem with the copy and paste function in superfields and shift = policies of super fields. If you copy the data in a superfield = that has an 'UPSHIFT' policy and paste it into a superfield that has = 'downshift' or 'noshift' policies it will appear the correct shift = policy until you focus out of the field. Then it turns to the = shift policy of the copied text. </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">This is a problem for us because when = a user enters query criteria in the field where the data was pasted, = they get no records found. </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">This is because the shift policy of a = given field is upper and the cut and paste function allows mixed case = to be entered and saved into the table. Query criteria is entered = in the field in whatever case the shift policy sets. To the user, = this data doesn't exist since they cannot get to it.</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Has anyone come across this or have = any ideas for solutions. I'm thinking maybe programming the = 'focus out' event of the superfield to change the case of the data to = the policy, but don't know how to do that.</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Thanks in advance,</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">Kathy Hildebrand</FONT> <BR><A HREF=3D"mailto:kathy%40htscm.com"><U><FONT COLOR=3D"#0000FF" = SIZE=3D2 FACE=3D"Arial">kathy@htscm.com</FONT></U></A> <BR> <FONT FACE=3D"Wingdings" = SIZE=3D2>J</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">Designer/Programmer</FONT> </P> </BODY> </HTML> ------ =_NextPart_001_01BDA123.3EF09B48--