Link to home
Start Free TrialLog in
Avatar of jansjobe
jansjobe

asked on

Strange view behaviour

This is a wiev somebody else designed, and I don't know how to get it right. I am very new to Lotus.

Web page display:
----------------------------------------------------------------------------------------------------

Country     Province     City
-------------------------------
Lagos
                A
                                 Bigtown
                                 Smalltown

Degas
                C
                                 Redtown
                                 Bluetown
...
A lot of other countries
...

Lagos
                A
                                 Mediumtown

----------------------------------------------------------------------------------------------------
End web page display


Why does not the country Lagos keep it's town's together????

Help me!

Best Regards,
Jan

ASKER CERTIFIED SOLUTION
Avatar of Sjef Bosman
Sjef Bosman
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of jansjobe
jansjobe

ASKER

You were right!
I'm at a very early stage of learning Lotus, and formulas are really out of my scope at this time...but thanks anyway!

Can I ask one more question:

A page is showing an embedded view. If there is no record matching; e.g. if the view is empty, is there a way to display a standard page, view or whatever (I told You, I am very new at this...) that says like "no record found"?
Piggybacking questions eh...? Not done usually, for several good reasons:
- many small questions get a larger audience than one large question with many unrelated issues
- when others are klooking for solutions, they use the title of the question to decide whether to open the question or not

For this once, you get your free ride :)

Yes, you can do that, but you need to program that, with hide-when formulas:
- one line "No records found", hide-when formula:
    x:= @DbColumn("":"NoCache"; ""; "Your embedded viewname"; 1);
    @If(@Iserror(x); @False; @Trim(x)=""; @True; @False)
- the hide-when of your embedded view must then be set to
    x:= @DbColumn("":"NoCache"; ""; "Your embedded viewname"; 1);
    !@If(@Iserror(x); @False; @Trim(x)=""; @True; @False)
Note the exclamation mark at the beginning of the last line (it's the logical NOT operator)
Sorry for piggybacking...should I make a new question?
I think I will need a little more guidance with this!
The more I look at this, the more I suspect that the person who originally made this database was even less skilled than me...

- There is one view for each page.
- The size of this thing is almost 1GB.
And there is only about 150 documents.

Also extremely many subforms.

Oh, maybe I should tell You that it is a database with Hotels, Restaurants, Cottages and other vacation related places adapted for various disabled people.
The idea is:

Country -> County -> City -> POI (point of interest)

At the moment it's like I have to hard code things down to every city; I do think that this seems exceptionally lengthy !!!??
The web page is also very ugly..

Maybe You could be hired to restructure things?

Best regards
Jan
I beg your pardon? 150 documents and 1 Gig? There must be a LOT of photographs in it, to get it that big. Since everything is hard-coded, it probably never happened that a view was empty :)

If you want me to have a quick look at the code (more is not allowed by EE rules), then
- make a copy of the database (without the documents!):
    File/Database/New Copy..., select Database design only, on your local disk
- close Notes
- zip the database
- mail it to me, you'll find my address in my EE-profile, somewhere in the middle
As you already said yourself, the database is poorly designed. Apparently, it's a Web-only database, but on the other hand I see no buttons to update a document from the web. The same form seems to be used in a browser. I suppose that, if the website is indeed for handicapped people, a special design could help them enormously. As you said, a database with 29 * 58 subforms can't be right...

There is too much to be done on the database to handle in a single question. There are two approaches possible:
- to attack one problem, convert the database, and attack the next problem
- complete redesign and conversion of the current database to the new one.

I'm sorry I don't have better options... :(