Problem #1 below. It is losing the formatting anytime I use SSNum in the
variable definitions in the whole form. It saves it with the dashes. It
displays it with the dashes, but everywhere else it is without dashes.
Help. I have dozens of forms that use the SSNum as a means for lookups from
another table.I hope there is a fix.Patti
On Saturday, December 4, 2021, 10:35:08 AM EST, 'Patti Jakusz' via RBASE-L
<rbase-l@googlegroups.com> wrote:
I need to clarify #2 problem below. It didn't stop in the middle of printing
a report. I ran a command file and I set output filename with screen and had
Echo on. It disconnected in the middle of printing a line in my file. It
disconnect halfway thru printing someone's SS#.Patti
On Friday, December 3, 2021, 07:34:48 PM EST, 'Patti Jakusz' via RBASE-L
<rbase-l@googlegroups.com> wrote:
Hello Rbase Pros,
We just finally upgraded from Rbase X to X.5 Enterprise and now I have problems.
1) I have forms that have formatted fields, using Input format masks. Our
SSNum has dashes in it and it's stored that way in the database. I have a form
where people enter the data for women referred to our program. SSNum shows up
on the screen with dashes. When I save it in the table it has dashes. But
when I use use it in an eep before saving the record, the dashes are gone.
I set a variable vss = SSNum in an eep that is run when you exit the SSNum
field. This is the point where the dashes disappear. I need to use it for the
next field, which has a pop-up menu using .vss
I know I can fix it by adding more code, but I hate to think of all the places
this might occur. Is this a bug? Does it have a fix? Has anyone else
experienced this? (I know I'm the only person in the world who stores SS# with
dashes, but I do.) This worked fine in all previous versions.
2. We now have a remote server, instead of one on-site. Rbase disconnects
users from the database at random times. It has nothing to do with inactivity.
I've had it disconnect me in the middle of printing a line in a report. It
happens in the middle of data-entry. They enter a bunch of small records.
Then the next record there is no connection to the database. It's crazy. The
server says we are not being dropped. But Rbase says we are.
Anyone else have this problem?
Thank you!!Patti
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/906679540.2411960.1638577982742%40mail.yahoo.com.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/605141476.2763414.1638631589311%40mail.yahoo.com.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to rbase-l+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/531048919.2386150.1638632744382%40mail.yahoo.com.
