Translated as.....

"In UML I defined a class named "storage". To implement I need it 2 tables and in both tables I need to update information, nevertheless the business object only allows for one table. Kevin made a comment where he said that the Business object could work with more than one table, using methods to be able to update 2 tables in business object and that the "standard" is to work on one table."

I think that's it, Rox. Man, too much Spanish, not enough coffee yet.


>en UML hice una definicion de una clase llamada storage, pero para implementarlo necesito 2 tablas, en ambas tablas necesito actualizar informacion , sin embargo el business object solo permite trabajar sobre una tabla, Kevin puso un comentario donde decia que el Business object podria trabajar con mas de una tabla, entonces que metodologia utilizaria para poder actualizar 2 tablas en un business object. ya que el "standard" es trabajar sobre una tabla
>
>gracias
>
>¿mi ingles es muy malo?
>
>:-)
>
>Greetings
>
>>>in this case i need n business objects for n tables, but the tables are implementation of class business object, in case i need n tables for modeling a single business object exist a approach? or methodology?.
>>>
>>
>>Francisco,
>>I'm sorry but I am having trouble understanding this comment, can you please explain again? Feel free to try explaining in spanish if that would be easier for you, there is always plenty of people up here that could translate for me. thanks.