0==========
原文(jiangjianxiao于2001/05/29 08:56粘贴) 
大家有无用vb实现com+组件好的模式建议 
--------------------------------------------------------------------------------
由于com+要求的无状态设计，com+组件被描述成一种仅过程的组件,在一些书上描述的com+组件好像都只有这样的方法 
getbyid ... 
save ... 
list .. 
不知道大家在具体实践中是如何设计模式的？ 

大家平时是如何处理这些问题的？（语言vb) 
在oop模式中，数据表格被映射称属性，但由于表格设计过程中一定会变化，导致接口被破坏，组件要不断的根据表格的属性调整 

根据事务的原子性设计，在每个操作中打开和关闭connection还是缓存它？？ 

在vb设计类似excel对象模式的组件时，如何防止内存问题？ 
呵呵，刚一来就提了一大堆问题。 

1==========
原文(nbmoon于2001/05/30 02:46粘贴) 
yes. I can answer some 
--------------------------------------------------------------------------------
I saw one method. They add a Object Model. they get the recordset through middleware. so you just modify the UI and Object when you change the database. There are one disadvantage in the method. You can not update the database by using recordset. Even you put the Object model in the middleware. you can update the database by using recordset, but can not pass the attributes to the presentative layer easily. 

If you need the connection in one transaction. you can open the connection at the first and close it finally. don't always open and close.