by shalom » Fri Oct 17, 2014 11:28 am
I figured out that I don't have to save each record, just load the database.
>First, please list Android specific reports in the Android forum as they are more easy to track.
Will do. I'm new to the forum and I wasn't sure where to report the bug.
- the Android device you are using LQ G Pad 410
- the version of Android operating system 4.4.2
- the formula used in the calculated field added 2 fields together ie f63+f65
- the result format in the calculated field float with 2 decimal places
- the conditions used in the conditional field I didn't get that far, as soon as I selected the Conditional type HanDBase quit working. It has happened a third time, so it seems to be pretty consistent.
If you have a database that helps to illustrate that, please include. I'm including the Order database (I've changed the DBpopup fields to a different type so it will be a standalone database). The field I was trying to change is zTL (Field 84)
> Regarding views, by default the first view in the list will be shown when opening a database. The order of the views can be altered when editing them. Alternately you can change default view via startup options.
I understand that, here is more info:
Catalog.dbf fields: IDno (text), Item (text), Desc (text), Club (popup), Category (popup), other fields
Club popup contains: Leader and 6 club names
Category popup contains: awards activity pages, uniforms, extras, ...
Units.dbf fields: Name (text), Club (popup), U1 (DBpopup), U1 (DBpopup), U1 (DBpopup), U1 (DBpopup), U1 (DBpopup), U1 (DBpopup), U1 (DBpopup), U1 (DBpopup), U1 (DBpopup), hCat (text defaulted to APg, the field is hidden), other fields
note: these DBpopup aren't grouped
Orders.dbf fields: Order Date (date), club (popup), category (popup), Item (DBpopup), IDno (DBpopup), Price (DBpopup), other fields
note: these DBpopup fields are all group 1
The Orders database needs to use the Orders view in Catalog to see the Item, Desc, and other relevant fields in order to pick a particular item to order. Also, it would be more user friendly if the records shown could be limited by the values in the Club and Category fields. In other words, a particular club and category can be selected in Orders to show only records in Catalog that match those fields, thus reducing the number of records to look through from over 800 down to around 30. SmartList allowed up to 3 fields for this type of filtering, but one field would be acceptable once concatenation ability is added.
The Units database needs to use one of the club views in Catalog to see the unit names to select from, and the records need to be limited based on the value in the Units Club and hCat fields to limit the records to just the ones needed for that club.
All of these views can't be set as the default and the user shouldn't have to change the view to see the correct fields and records. Also, separating the units info to another database would require double the work and maintenance. There are other similar situations in the database system I did in SmartList that I need to be able to do in HanDBase.
I hope I explained it well enough.
Thanks for giving this your time and attention.