>>Anyone here want to comment on the issue of
>>whether on not to make your stored procedures as
>>objects.
>if by "stored procedures" u refer to the code
>stored in the DBC
>for use as RI code and Triggers
>then i can assure u that writting RI code is
>complex enough
>as it is
>as for triggers, i guess this can be done but in
>the actual trigger u'd have to have a procedure
>that will instantiate
>the object
>
>Arnon

I am working with a client that says FoxPro will probably work for him for the next year or two, but he must move up to something like Oracle or Sybase to handle the large tables. All the stored procedures that I write are going to go to waste unless I model them in OOP, maybe?