I always like to have my phone #s use this format: 000-000-0000 AND to save the mask in the data.

if I get some data from a foreign source, or a text field that didn't use that Mask, and then that data gets put into my phone # field, when that record gets edited, the phone # will "look correct" when displayed on a Form.

Whats confusing to a user is that if they Edit this record, and don't do anything, and try to close the Form, they will get the dialog "There are unsaved changes in the form of object QuoteRequest.
Do you want to save them?"

Its confusing because the user didn't do anything. He opened the form, and closed it.
I know why this is happening, but does anyone else struggle with this in their data or users?

Better scrubbing of the data would work - or making sure the phone # is entered correctly to begin with.
Is there a function to format data according to an input mask?

    Jaymer
    Sounds strange and like a bug i.e if the form hasn't been changed, Aware shouldn't ask that question when trying to close the form? Or did I miss something i.e is this default Aware behaviour for some reason?

    Not exactly a solution but try VIEW VS EDIT and see if there is a difference? I sometimes use VIEW to circumvent things like this, in some cases Aware works in mysterious ways lol so quicker to work around.

      Has nothing to do with view versus edit And it’s Technically not a bug.

      I said that I know exactly what is happening… It’s because the phone number is stored without the input mask, which are hyphens or dashes.
      When the form is displayed the phone number now has the dashes.
      When the form is submitted, aware says that the data has changed, which it has.
      To the user though, he didn’t do anything, but literally the phone number field is now 12 characters long, which includes the two dashes, instead of 10 characters long like it Used to be Without dashes.

      Again sounds like a bug to me i.e this is not how it should work. Regardless of what the data is and how it is presented, the user hasn't actually changed anything i.e they should not get the error when closing the form.

      Regarding the VIEW VS EDIT, Aware handle these in a different way (as I am sure you are aware) and if you use EDIT, Aware is waiting for changes which means when you close the form, Aware asks about saving changes. If you use VIEW, Aware doesn't wait for changes i.e when you close the form, Aware knows no changes have/can be done i.e you may not get that question. I have used this for similar scenarios before and I have also at times (and this might work even using EDIT) used a custom "Save" and/or "Close" button which isn't the form default save/close but instead a process lets say that bypass the form save (and hence bypass the Aware save ask problem). My point is that you can probably tinker to a working workaround using something like this.