----------------------------------------------------------------------------------
@MSGID:
<03d2fc13-d234-4f7c-8362-98fa0451a96bn@googlegroups.com> 0f7a4a42
@REPLY:
<6c679c69-5ac9-4b24-9dc3-f79f621b1f2bn@googlegroups.com> 9ac02cb0
@REPLYADDR John Pollard <8plus7isf@gmail.com>
@REPLYTO 2:5075/128 John Pollard
@CHRS: CP866 2
@RFC: 1 0
@RFC-References: 1@dont-email.me>
2@dont-email.me> <6c679c69-5ac9-4b24-9dc3-f79f621b1f2bn@googlegroups.com>
@RFC-Message-ID:
<03d2fc13-d234-4f7c-8362-98fa0451a96bn@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Wednesday, September 20, 2023 at 1:34:01 PM UTC-5,
John Pollard wrote:
> Since the problem is easy to reproduce; I suggest you create a
> Quicken test file with one account that demonstrates the problem.
> Then use the Quicken Help > Report a problem feature to tell
> Quicken about the problem - and send the test data file with the
> report.
I probably should have added that Quicken will popup an error
message when it detects a disallowed character in an account
name -- so if Quicken doesn`t want em-dashes in account names,
it should popup that same error message when it detects an
attempt to use that character in an account name.
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441