Hi Steve.


>Just because you can, doesn't mean you should :)

.T. - but personally I have used UDF's in an index expression and not ever had a problem - although not in the way that Wayne was trying it. I think Wayne was perhaps given the impression that its never ok to use a UDF in an index - which it is ... sometimes.


>Jim pointed out to him the danger of using the UDF...the index will break when someone changes the name in the related file. So to help him make the UDF "work" would have been bad help, right?

.T. and .F. - Showing how it can be done and highlighting the danger is the best of both worlds. Wayne can then decide how to take it further for his own particular project.


Have a good one!


>
>>Hi Steve. PMFJI but I think what Wayne is asking is why one cannot use a UDF in an index and the short answer is you can. Its ok to do so but adds an additional level of complexity to the structure. In addition, it would appear to not be optimal or perhaps even necessary in his particular post.
>>
>>
>>>Hello Wayne,
>>>
>>>3 people have addressed the issue: you shouldn't be using a UDF for the index. You don't need to use the view wizard in order to make a view. See CREATE SQL VIEW in help and use the AS SQLDELECTStatement clause.
>>>
>>>Before you actually create the view, you can work on a SELECT statement in the command window that returns the results you need. If you need help with the JOINS, show your table layouts and folks here will give you help.
>>>
>>>>I have 1 parent table, 2 child tables and 1 grandchild table. I can relate the parent to 1 child and then to 1 grandchild. I cannot relate the parent to a second child table in a view (according to the view wizard). I still don't understand why I can't get an index based on a UDF to work. Nobody has really addressed that issue.
>>>>
>>>>Thanks for your help.