#BUG FIXES
O.K. an update is on the way to correct a few minor bugs, but what bugs ???
Right now I can't save a form with command strings attached to the
pushbuttons(see my previous message). Steve may find this a minor
inconvenience in queries and reports, but when trying to design forms with
added validations this is a MAJOR pain.
Since I'm new to SBP4, and believe in K.I.S.S., I was working with a
single file. What I wanted to do was enter a customer ID number (a home
phone) and if it already exists show the record, else enter the data as a
new record. I can simulate the auto-pushbuttons with function keys and it
seems to work great, but if I can't save the commands on a form it makes
for lots of extra key strokes.
Is this one of the bugs that's to be fixed, or am I wasting a lot of
time trying to learn a phantom feature ?
By the way how did you save those forms on the examples disk ? If I try
to modify them the command strings disappear too.
While I'm asking questions, is there a way to modify the data entry
order from DML ? I tried to add pushbuttons to the form via the add form
commands, but when I tried to assign them a data entry number in the middle
of the form, where they belong, status shows multiple fields with the same
data entry numbers ??? If not is there a way to leave empty spaces via the
form designer ? Couldn't get it to work right yet anyway.
Also, there doesn't seem to be anyplace to put a button title in the add
form command, or am I missing something ?
So far, barring the above problem this looks like a great program.
Hope to hear from you soon
Roger LeVine