Jean-Marc

I just figured out why I was having trouble with my filter searches for plants assigned combination values. I should have used the "contain" parametre rather than the "is". So, I'm back to being happy with the plant reference database. I still am concerned about the implications of not being able to synchronise the Plant Reference DB with the Utility...

1. So, then what are the implications regarding this inability to synchronize the plant list with the utility? Once I have customized the Plant Reference List, does it mean I will run into problems should I ever want to import a new plant list into reference list via the utility? 2. Also, I'm back to thinking that the plant reference list is significantly flawed, at least for my purposes. Following your instructions, I've customized some of the attribute values. Unfortunately, it turns out that the combination values you suggested do not work well when custom filtering. Using your example, I created a "Wet Feet and Drought" value under Tolerances, and a "Sand, Loam, Clay" value under soil range (among other potential combo's), to reflect the fact that many, if not most, plants can tolerate a range of conditions. Now, say I want to set up custom filter to select plants for a sandy site that is drought prone, but never wet. When I set up a custom filter to search for drought tolerant plants that can grow in sand, none of the plants assigned a combination value will turn up, as I must enter the exact character string used in the field. I am not a happy camper... I based my decision to purchase Landmark largely on the basis of the plant database, which would now appear to be largely unreliable. Also, I think it is misleading for VW to use the term plant "ranges" if I cannot in fact select a range of conditions.

Thanks Robert, it is indeed helpful to know that the Plant Reference Data categories are customizable. It still doesn't solve the problem entirely, as there can be any number of catagory/value combinations for plant tolerances, landscape uses, and flower, foliage, and fruit characteristics, and there is no way I'll be trying to set up combination catagories for all the possible permutations. It would be more effective to simply be able to select more than one value per plant attribute, as required. As it is indeed important to synchronize the Utility with the database, I agree it would be helpful if you could provide some direction on how to edit the Utility. , depending on the species. of values and allow additional "multi-range" values to be added, per the process described below: ----------------------- Let's say you wanted to add a combination category of "Drought & Wet Feet" to Tolerances. Here's what you'd do: Yes, it is helpful to know that the

One of the reasons I just purchased Landmark 10 was for the Plant Reference Database and the filtering options it provides in developing plant lists. I've begun expanding and revising the species list, and in the process, have come across what seems to be a glaring weakness in the program (or I'm just not getting something). Is there any way to assign more than one field selection for the plant ranges? Many plants, for instance, have two or more environmental tolerances (for instance, wet feet and drought) or can tolerate sand, loam, or clay soils, or can tolerate full sun to full shade. I've been using the VWL Plant DB Utility to perform my edits. The utility does allow me to assign more than one selection per field using the Ctl key. However, when I import the reference plant list into the Landmark and access it from the Plant Reference Database, the data is all scrambled, data from the new records spills over into other plant records - in other words, its a mess. If I can't assign ranges to the plant ranges fields and am limited to only one possible selection, then this database will generate flawed plant lists and is therefore of little use to me. Can anyone help?