Embedded Browses on Tabbed Form

[DaveM]

Re: Embedded Browses on Tabbed Form

An alternative to tabs is a conditional object(really like tabs) with more abilities. Might want to look into that. Again you set a variable to each condition(1 variable and change it) you want to show. I totally dropped tabs for these. They are almost the same as tabs as they are layered on top of each other and I have been told they are really tabs but witout the tab on top. They seem to work better for all the apps I make and where they are needed.



Hope it helps- each button(no - they are not tabs) you see like weights, gears, etc just changes the value of the var and does a refresh.

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

Stan
How do I use the variable in the filter for the lookup. At the moment my filter the filter reads between(Product_Id,"520111","520399") .or. between(Product_ID,"520811","520895"). This determines what segment of the Products Table (BOM) is shown in the drop list on the embedded browse. The aim is to have all the different categories shown in the same order report i.e. Meat, Bread, Deli, Dry Goods, etc.

Stan
I have done it and you are quite right, as always, it is messy :-
((Var->act_tab = "Loaves" .and. between(Product_Id,"520111","520399") .or. between(Product_ID,"520811","520895"))) .or. ((Var->act_tab = "Individuals" .and. between(Product_Id,"520111","520399") .or. between(Product_ID,"520811","520895")))
and this is only 2 tabs out of 11. I am trying to think of a neater way and any donations will be appreciated. We will be in Rotonda, Florida during February 2012 and if you would like to drive down I will buy you a large glass of lemonade!

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

DaveM
Thank you for that, it is very similar to the old Superbase system of having a form with pages that were 'stacked'. When are you guys going to go metric, even dear old blighty is now almost metric. We have a few quirks especially with Timber(Lumber); you can still order 2 x 1 (50mm x 25mm) but it will come in metre lengths. The roads are still measured in miles (country miles are longer than town miles) but we buy our petrol(gas) in litres. I will never get use to measuring fuel consumption with so many litres per 100 kilometres.

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

Stan if this is a repeat I apologise, but my reply seems have to disappeared. Thanks for the solution and you are quite right it is a messy way of doing things, the filter now looks like this :- ((Var->act_tab = "Loaves" .and. between(Product_Id,"520111","520399") .or. between(Product_ID,"520811","520895"))) .or. ((Var->act_tab = "Individuals" .and. between(Product_Id,"520111","520399") .or. between(Product_ID,"520811","520895"))) and that is just two tabs out of eleven! Any advice would be greatly appreciated.

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

This is an easy one - The label of one of my Tabs is "Fruit & Veg", but Alpha insists on using the "&" as a short cut control (I do not know the correct terminology). Is there a way of telling Alpha this is a literal?

[Stan Mathews]

Re: Embedded Browses on Tabbed Form

, the filter now looks like this :- ((Var->act_tab = "Loaves" .and. between(Product_Id,"..........

But what if the table had another field (t_type) and you populated each record with the text of the tab upon which the item should appear?

Then the filter could be

t_type = var->act_tab

[Stan Mathews]

Re: Embedded Browses on Tabbed Form

Alpha insists on using the "&" as a short cut control

This has been discussed before, why not practice your search techniques. (Also best to start a new thread when the question wanders off topic.)

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

All the best ideas are the simplest ones. Job done.

[Stan Mathews]

Re: Embedded Browses on Tabbed Form

I have to keep it simple or I couldn't understand it.

[Stan Mathews]

Re: Embedded Browses on Tabbed Form

I would suggest that you, in either the autoexec script or the oninit for your startup form, dim the act_tab variable as global and assign it the text of the first tab on the tabbed object.
dim global act_tab as C
act_tab= "Loaves"

Doing that means there will always be a value set for act_tab and when you open the form the value will be what you want to filter the browse on the visible tab.

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

Stan
You are a good mentor, I have already done it. Do you think there is a chance for me yet?

[Stan Mathews]

Re: Embedded Browses on Tabbed Form

You'll be answering posts before you know it.

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

Stan
I am not being sycophantic, but that code was brilliant in its simplicity; I have only just implemented it. I added two fields to the Product Table - "Category" and "RptOrder" and populated them with the Tab Label text. The second field was required for the Orders Report because the Product_ID's were not contiguous and are not in the order required i.e. Bread has a Product_ID in the 500000 range and Meat starts at 011080 but the Client wants Bread reported first. Thanks again.

[Ted Giles]

Re: Embedded Browses on Tabbed Form

Back and sun tanned Ron.
Just had a butchers (no pun intended) at the Db you posted. Looks pretty comprehensive if a little confusing.
"If you want to use the Page Up/Page Down keys, click on the Save Record button otherwise you will scroll up and down in the items list" ? A shop full of customers and I have to think about this?

Not suggesting you change anything, but you will notice the difference in approach if you view the Alpha Sports sample app. Smaller and more descrete bits of information. Too much info on one screen sometimes overwhelms a new user - and you will have to teach them I suspect. Consider the impact on a total novice. Try it on a friend with little interest in computers. I say this from a position of having overcooked a system for a Milkman some years ago - my first in fact. Covered all sorts of products and delivery schedules for 6 delivery men as well as the usual order changes brought about by holidays etc. In the end, I added a "YOU ARE AT THIS POINT IN THE PROCESS" button with a schema showing exactly where the user was in the order entry, confirmation, billing process.

On a lighter note, I suspect you may have issues with the Product_ID using ranges of numbers. The Category also looks a bit long winded in the BoM.

[Ron Cooper]

Re: Embedded Browses on Tabbed Form

Thanks Ted
I hope you had a good holiday. A lot has happened since you 'deserted me'. I have re-written most of it. The BOM now has two simple fields, one with a range of 10 items - Bread, Meat, Fruit & Veg, etc. The second field is propagated by the former with a series 01,02,03 etc. This is because the Report Order does not follow the Product_ID number. The BOM is imported from Quick Books and most of the fields are redundant to my system, but it gives the Client comfort. I am now trying to convert the Order file into a Invoice File that can be imported into Quick Books. Do you know anything about the file structure of Quick Books (Intuit)?