General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
>>>>This is a function you wrote? Couldn't you pass the name of the field?
>>>
>>>Yes Nancy, but I wondered if one could. It's not earthshaking if I have to pass the name of the field. Perhaps I've gotten too used to being able to get that sort of info :)
>>
>>Er..what "sort of info?" I'm trying to think of an analogy, and am not. I'll be terrifically interested to hear if the runtime exposes to a function the field that has triggered a default expression call. Perhaps, somehow with 7.0 database events, it's more possible to control that.
>>
>>But, with GetID() functions, for example, I've always done, and have always seen others do this, too...that is call the func with the table and field name (unless one can _assume_ what the field name is).
>
>Nancy,
>
>By "that sort of info" I meant the following, for instance:
>1) If parameter is tcAlias, but it wasn't passed, use ALIAS() as default;
>2) If parameter is tcDBC, but it wasn't passed, use DBC() as default
Yes, I see. But the functions ALIAS() and DBC() in any function have meaning independent of the context in which a UDF is called. There is no corresponding "active field" notion (whether empty or not) in VFP which is what you'd need for your idea to work.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only