SBPro4 problems
10 messages in this thread
Pat,
I am having a number of problems with Superbase Pro 4. I am running on a
2500 under OS 1.3. I am about to upgrade to 2.04 in the next week.
Problems in order are:
1) I have a database called Invoices which is unable to open without an
error.
The error message is "Problem positioning in data file". I have
reorged the
file as per documentation and had no luck. I have used Query to
extract the
contents of the database to a new copy. No luck. I have deleted and
re-
created the indices (7 or 8 of them at last count). The file will
actually
open if the Project-Open-File is used again or if the DML "Open File"
is
reissued. 99% of the time, Superbase's menus are trashed and the
machine
will GURU or simply hang.
2) When using COMMS to attempt to receive a file from my client (in
Orlando;
I'm in Miami) my modem will not answer. Using something like JRCOMM
works
fine. I have Auto-Answer mode enabled on the modem.
I will have to write down specifics of other difficulties I am
encountering and send them to you in another message. As far as the problem
above (#1) I will be happy to upload the required databases if you require
it. My disk's serial number is 10C45755.
Any help would be appreciated. Thanks in advance…
Jim Joslin
Jim:
First, are you using version 1.0 of the Superbase Pro4 program? If you
are, you need to get the FREE update disk to version 1.01.
Second, are you using a GVP hard disk or controller card?
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227
Pat,
I'm using a GVP 68030/68882 at 36MHz and a GVP Series II SCSI controller.
Is there a problem with that?.
Ciao, Neil
The problems we have noticed are with using the Commodore Installer program
and the 1.0 version of Superbase Setup (fixed in version 1.01). It may have
something to do with the small maximum transfer size set up as default when
the GVP controller is installed. If you have had problems, you should
contact Great Valley and ask about the possible fixes for the controller
setup.
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227
Pat,
I haven't noticed any problems, but if I have any, a close friend of mine
is the guy who writes all of those drivers. In fact, the CD-ROM filing
system I am currently using was written by him and I don't think it is even
on the market yet. I also translated his book, which may even make it on
the shelves if we can ever finish editing it. It was considered to be the
*best* book on Amiga programming ever (over here anyway), and will be
coming out in an English language version including support for 2.04 as
soon as we finish the last bits. It is currently about 700 pages, and in
the previous format, would have required over 900 pages.
Ciao, Neil
Pat,
I have 1.01 of SBPro4. I have a stock 2500/30 with a 2091 and Q105s.
I talked with Mike @ Oxxi reference my difficulty. I told him I was going
to send him a disk with the full implementation of my application on it,
however a little bit of minor surgery got in the way.
As I stated in the earlier message, I was getting a message "Problem
positioning in data file" while my opening my "Invoices" database. After
thinking about it a while, I decided to strip the database of any and all
cross-file validations (i.e.; LOOKUP) and start essentially from scratch. I
had validations in the database for 5 reference tables. I added each
validation back one at a time and eventually hit on the file that was
causing the problem in the first place. I spent a good week reorganizing
the Invoices database per the docs for no gain. I blew away the offending
table and reloaded it and solved the problem. I still have no idea why the
menus (the ones which belong to SuperBase) got trashed every time I got the
error. Or why Superbase would go off to la-la land.
As my immediate problem is solved, I have yet to mail a disk out. I will
be more than happy to send it if you so desire.
I do have a suggestion though as to how to make the situation I ran into
a little bit easier to handle… just include the name of the file there is
a problem positioning in in the message instead of being cryptic.
Thanks,
Jim
I have been having a constant problem with "Error positioning in file…"
problems when altering records in a file. Finally came to the conclusion
(and verified) that at least one condition that trashes the index pointers
is indexing on a calculated field that does not re-calulate on the first
save after a change. This condition can exist if you have added or changed
calculated fields (in my case needed to manipiulate incoming data into the
format I need in my system) and they are not in the right order. Problem
went away (on this file) when I recreated the file with the fields in the
right order. I suspect that your LOOKUP related problem could be from the
same set of conditions: the index field is not being updated at the right
time.
– via Whap!
Interestingly enough, the file it turned out I was having a problem with
was a static (read unchanging) database. It contained a grand total of
three records. The file was created and loaded manually. However, I'll keep
your info on file for future reference. Thanks much.
Jim
Thanks, Loren. We have a standard statement from the SBase programmers "in
the know" — most problems with LOOKUP are caused by incorrect entry order
or operation order.
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227
Jim, I'll make sure Mike gets the suggestion. One of things he is
committed to doing is making the error messages from the program supply
more information to the user. In some cases, this may not be possible (for
example, the infamous "Error reading block 200" message could be modified
to state "Operation encountered deleted record", but it might not be
possible to add "in file {name}" without re-triggering the error), but
certainly for your problem, it sounds as if this information could be
added.
Thanks for the succinct re-statement of your problem here, it helps to get
things fixed so others don't encounter the same problems in the new
version.
Regards, Whap!penned…
Pat @Oxxi (310) 427-1227