#Form Data Entry Font
8 messages in this thread
I have a question about data entry in a form.
I have some fields in the form set in a very small font, so they will fit
on the page. Superbase displays them properly, but when I edit the data in
a field, while I am editing the data shows up in the default system font,
which is too large for the data entry area. It is annoying.
1. How can I tell SB that I want to edit in the default display font for
that field, and 2. If I wanted to change the system (global display) font,
how would I do it?
-E Cottle
– via Whap!
Mr. Cottle,
The font will always change to the system font while editing on a form.
There is no way to keep this from happening.
Darin, SPC Superbase Technical Support
– via Whap!
Thanks for the prompt, direct response. I guess if you keep track of
user requests for future enhancements, that would go on the list.
May I follow up? I can't find any information in the manuals about how to
change the default system font. Is that possible?
I also have a few other questions.
The SET REQUEST command lets me turn off some messages, but apparently not
all of them. For example, when I ask SB to duplicate a record, it will
always tell me that a new record has been created for editing. After about
the 50th time, I start wishing I could turn that one off, because it really
slows things down. However, even after a SET REQUEST 255, it keeps coming.
I believe I have asked this one before, but I don't recall ever getting a
response. In a transaction form, is there any way to control the order of
the records in the transaction lines? For example, if a form links an
author database with a books database, and that form shows author
information, followed by transaction lines showing all books by that
author, is it possible to get the form to list the books alphabetically?
Thanks again.
E Cottle
– via Whap!
I have passed this request on to the people who are now doing development
on the Amiga Superbase product.
Regards, Patricia Cummings @ Oxxi (310) 427-1227
Pat,
Thanks for the info. If you are interested in more feedback, there are a
couple of other things which could be done to improve the comfort level of
using SB.
1. I left a question about sorting transaction lines. I understand the
system cannot handle that yet. That would be useful enhancement.
2. Anytime I make a change to fields on a form, even something as simple
as moving or resizing the object, the forms editor forgets the data entry
order and field justification I had set.
3. SB Tech support has not yet answered a couple of my questions, so I am
not sure whether I can turn off the 'duplicate record created…'
requestor. If not, it would be nice to be able to turn it, and any other
requestor, off.
Let me know if I should be directing these suggestions to someone else. I'm
sure I will have more as time goes on.
Thanks.
-E Cottle
– via Whap!
There is a couple of ways to sort transactions, but you will have to decide
if the work is worth it. I opted to wait until the system supports it but
if you wnat to do the work, implement a dummy file for the transaction
lines and create an array big enough to hold *all* of the transactions that
may ever be required for a single master record. Then fill this array each
time a record is selected and then update each line that is visible on the
set of transaction lines using UPDATE FORM ROW. To say the least, it is a
lot of work and you lose the use of the browse panel. If you want to know
more, watch for Superbase Supercharged coming soon from Bantam.
Neil,
Thanks for the info. I have been impressed with superbase overall, but I
find it has some curious, annoying restrictions. In general, the more
sophisticated a software package is, the more flexible it is with regard to
letting you do what you want with it. The restrictions I have found in
superbase seem out of place in what is otherwise an impressive software
package.
-EC
– via Whap!
Superbase is a product in transition. One of the reasons for the
restrictions is that there was simply a limit to how much a 3 man
development team could accomplish when supporting both the Amiga and the
Windows platform. That has changed now. The Windows product is owned by SPC
and the original development team has been bought up to 8 programmers and
scads of support personnel. The Amiga version has been sold to Oxxi with a
source agreement that will allow the Amiga version to have the capabilities
of the Windows version. Give it a little more time and I think (almost)
everyone will be pleased.