--- In [email protected], "Sheri" <sheri...@...> wrote: > > --- In [email protected], "entropyreduction" > <alancampbelllists+yahoo@> wrote: > > > > > ActiveConnection: Sets or returns a String value that contains a > > > definition for a connection if the connection is closed, or a > > > Variant containing the current Connection object if the > > > connection is open. Default is a null object reference. > > > > > What do you think? > > > > I'd hasve to read your code more closely than I have so far to say. > > > > Will look at it this weekend.
So you'd call OpenAccessData from OpenAccessView, release mydb in OpenAccessData, MakeVector would never see mydb? That boils down to: can a "ADODB.RecordSet" object exist even though the "ADODB.Connection" from which it was generated is gone (in the sense of underlying IDispatch* released?) No idea, try it and see. > This script might also be useful if you want at some point to look at the > possibility to accommodate a return that is an array. If the com plugin could > handle it, myview.getrows would return a Variant that is a two-dimensional > array. Using that would probably be much more efficient than what my script > does for collecting the data: one com call call instead of one per field per > record. Entirely academic for my own meager data! But still ... maybe the com > plugin could create a handle to the returned data for data types not > currently accepted by the com plugin, which could then be read by the dll > plugin? Probably easier to look into handling SAFEARRAYs, which is I presume what myview.getrows returns. SAFEARRAYs are a bit of a nightmare, but will look into them eventually. > For later looking to the other side of the equation, one of getrows' optional > input arguments can be also be an array (in this case a single dimensional > array of field names). OKay. Also on my list: get more stuff in dialog plugin to deal with out-of-process dialogs maybe update database plugins to build on what you've done and populate class instances.
