Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7200 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have a credit card field that I would like the first 12 digits to use the bulletz font and the last 4 to use the arial font. Is this possible? I haven't been able to get it to work but wasn't sure if it wasn't possible or if it was the way I was using the TextFont function. This is the 1st time I have used the TextFont function.

Thanks,

John

Posted

I have a credit card field that I would like the first 12 digits to use the bulletz font and the last 4 to use the arial font. Is this possible? I haven't been able to get it to work but wasn't sure if it wasn't possible or if it was the way I was using the TextFont function. This is the 1st time I have used the TextFont function.

Thanks,

John

Posted

I have a credit card field that I would like the first 12 digits to use the bulletz font and the last 4 to use the arial font. Is this possible? I haven't been able to get it to work but wasn't sure if it wasn't possible or if it was the way I was using the TextFont function. This is the 1st time I have used the TextFont function.

Thanks,

John

Posted

Probably yes. But as a security measure it's only a copy and paste away from clear text.

Posted

Probably yes. But as a security measure it's only a copy and paste away from clear text.

Posted

Probably yes. But as a security measure it's only a copy and paste away from clear text.

Posted

If you are talking a simple display field, the answer is yes.

If you are talking a data entry field, the answer is no. The reason is that you can't establish a 'zone' for part of an entry field.

Of course the answer is simple, split the credit card number up into 4 (or 2) separate fields. However, Vaughn is right; now matter what I can think of to obscure part of the CC number, it is vulnerable to copy'n'paste should someone figure that out.

Posted

If you are talking a simple display field, the answer is yes.

If you are talking a data entry field, the answer is no. The reason is that you can't establish a 'zone' for part of an entry field.

Of course the answer is simple, split the credit card number up into 4 (or 2) separate fields. However, Vaughn is right; now matter what I can think of to obscure part of the CC number, it is vulnerable to copy'n'paste should someone figure that out.

Posted

If you are talking a simple display field, the answer is yes.

If you are talking a data entry field, the answer is no. The reason is that you can't establish a 'zone' for part of an entry field.

Of course the answer is simple, split the credit card number up into 4 (or 2) separate fields. However, Vaughn is right; now matter what I can think of to obscure part of the CC number, it is vulnerable to copy'n'paste should someone figure that out.

Posted

As an FYI -

You could create an auto enter calc with the option Do not replace existing contents (if any) turned off.

This could look like


Let (

[ bulletz = TextFont ( Left (your field here;12); "Bulletz" );

  arial = TextFont (Right (your field here;4); "Arial")];



Bulletz & Arial

)

This would change the contents of the field to be bulletz followed by arial after the user entered the initial value (and would stay that way until otherwise changed)

But see Vaughan's post for security isues.

Posted

As an FYI -

You could create an auto enter calc with the option Do not replace existing contents (if any) turned off.

This could look like


Let (

[ bulletz = TextFont ( Left (your field here;12); "Bulletz" );

  arial = TextFont (Right (your field here;4); "Arial")];



Bulletz & Arial

)

This would change the contents of the field to be bulletz followed by arial after the user entered the initial value (and would stay that way until otherwise changed)

But see Vaughan's post for security isues.

Posted

As an FYI -

You could create an auto enter calc with the option Do not replace existing contents (if any) turned off.

This could look like


Let (

[ bulletz = TextFont ( Left (your field here;12); "Bulletz" );

  arial = TextFont (Right (your field here;4); "Arial")];



Bulletz & Arial

)

This would change the contents of the field to be bulletz followed by arial after the user entered the initial value (and would stay that way until otherwise changed)

But see Vaughan's post for security isues.

Posted

It can be only a display field, that is no big deal. We don't want the processors to be able to see all the numbers. So what do I set the fields font to be initially, Arial or BulletZ? Maybe it doesn't matter?

Thanks for the help!

John

Posted

It can be only a display field, that is no big deal. We don't want the processors to be able to see all the numbers. So what do I set the fields font to be initially, Arial or BulletZ? Maybe it doesn't matter?

Thanks for the help!

John

Posted

It can be only a display field, that is no big deal. We don't want the processors to be able to see all the numbers. So what do I set the fields font to be initially, Arial or BulletZ? Maybe it doesn't matter?

Thanks for the help!

John

Posted

If you don't want them to see it, what's the point in showing it as bullets?

Make your field Right (CC# ;4 ) and show that.

If you really want this, you can put a text object on the layout, containing 12 bullets followed by a merged field showing the last 4 digits.

BTW:

TextFont ( "xxxxxxxxxxxx" ) ; "Bulletz" ) & TextFont (Right ( CC# ; 4 ) ; "Arial" )

can be copied and pasted with no security problems.

Posted

If you don't want them to see it, what's the point in showing it as bullets?

Make your field Right (CC# ;4 ) and show that.

If you really want this, you can put a text object on the layout, containing 12 bullets followed by a merged field showing the last 4 digits.

BTW:

TextFont ( "xxxxxxxxxxxx" ) ; "Bulletz" ) & TextFont (Right ( CC# ; 4 ) ; "Arial" )

can be copied and pasted with no security problems.

Posted

If you don't want them to see it, what's the point in showing it as bullets?

Make your field Right (CC# ;4 ) and show that.

If you really want this, you can put a text object on the layout, containing 12 bullets followed by a merged field showing the last 4 digits.

BTW:

TextFont ( "xxxxxxxxxxxx" ) ; "Bulletz" ) & TextFont (Right ( CC# ; 4 ) ; "Arial" )

can be copied and pasted with no security problems.

Posted

Because it makes our processors feel warm & fuzzy! smile.gif

I may use your suggestion of a text image and a merge field. That would be simpler than distributing the bulletz font to everyone.

BTW:

TextFont ( "xxxxxxxxxxxx" ) ; "Bulletz" ) & TextFont (Right ( CC# ; 4 ) ; "Arial" )

can be copied and pasted with no security problems.

Not if you don't allow them to enter the field in browse mode.

Thanks for the suggestion!

John

Posted

Because it makes our processors feel warm & fuzzy! smile.gif

I may use your suggestion of a text image and a merge field. That would be simpler than distributing the bulletz font to everyone.

BTW:

TextFont ( "xxxxxxxxxxxx" ) ; "Bulletz" ) & TextFont (Right ( CC# ; 4 ) ; "Arial" )

can be copied and pasted with no security problems.

Not if you don't allow them to enter the field in browse mode.

Thanks for the suggestion!

John

Posted

Because it makes our processors feel warm & fuzzy! smile.gif

I may use your suggestion of a text image and a merge field. That would be simpler than distributing the bulletz font to everyone.

BTW:

TextFont ( "xxxxxxxxxxxx" ) ; "Bulletz" ) & TextFont (Right ( CC# ; 4 ) ; "Arial" )

can be copied and pasted with no security problems.

Not if you don't allow them to enter the field in browse mode.

Thanks for the suggestion!

John

This topic is 7200 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.