Lyle, do you find those operations useful in the "normal business
databases"
for which Access is so well-suited, or just when using an ADP as a
front-end
to MS SQL Server? I don't seem to recall, in using Access since its
inception, a _need_ to "get a table/query as a string". Most of my
clients,
even those with MS SQL Server, did not want any vital applications created
that would limit their ability to change the server back end if their
company decided to do so. Thus, ADO's were unacceptable to those clients.
Refresh my memory: didn't you write that you, for good reason, stopped
using
ADPs?
Or are you talking about using ADO in an MDB/MDE/ACCDB? I'm reluctant to
use
a data access technology that has already been superceded in its "natural
environment" (Microsoft's developer tools) by ADO.NET which is little like
"classic ADO" (as I am sure you are aware).
Larry Linson
Microsoft Office Access MVP
"lyle fairfield" <lyle.fairfield@[EMAIL PROTECTED]
> wrote in message
news:fdd585d9-7f9a-4a17-9cc9-fc176986d80c@[EMAIL PROTECTED]
Jun 29, 12:09 am, "Tony Toews [MVP]" <tto...@[EMAIL PROTECTED]
>
wrote:
> lyle fairfield <lyle.fairfi...@[EMAIL PROTECTED]
> wrote:
> >You're right. It's still going strong, the same old unsophisticated,
> >ugly, clumsy technology we knew and loved almost,twenty years ago.
>
> >Why does MS cling to it? IMO it's this way. MS wants to sell Access.
> >There are more people who are lazy and/or stupid than there are who
> >are smart and/or industrious. So their marketing is aimed at the lazy/
> >stupid majority. Here you go, bozos, a database you can use with no
> >effort, training, learning caring or education. A new, sophisticated
> >technology scarcely fits with that, does it?
>
> ADO has some new features that I'm aware of but none seemed
> particularly useful to me.
>
> From what I've seen ADO and DAO don't have a lot of differences. So
> what else or what improvements would you suggest?
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems
> athttp://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
----------------------
GetString Method (ADO)
Returns the Recordset as a string.
Variant = recordset.GetString(StringFormat, NumRows, ColumnDelimiter,
RowDelimiter, NullExpr)
-----------------
Save Method
Saves the Recordset in a file or Stream object.
recordset.Save Destination, PersistFormat
Parameters
Destination
Optional. A Variant that represents the complete path name of the
file where the Recordset is to be saved, or a reference to a Stream
object.
PersistFormat
Optional. A PersistFormatEnum value that specifies the format in
which the Recordset is to be saved (XML or ADTG). The default value is
adPersistADTG.
--
Open Method (ADO Recordset)
Opens a cursor on a Recordset object.
Parameters
Source
Optional. A Variant that evaluates to a valid Command object, an
SQL statement, a table name, a stored procedure call, a URL, or the
name of a file or Stream object containing a persistently stored
Recordset.
ActiveConnection
Optional. Either a Variant that evaluates to a valid Connection
object variable name, or a String that contains ConnectionString
parameters.
CursorType
Optional. A CursorTypeEnum value that determines the type of
cursor that the provider should use when opening the Recordset. The
default value is adOpenForwardOnly.
LockType
Optional. A LockTypeEnum value that determines what type of
locking (concurrency) the provider should use when opening the
Recordset. The default value is adLockReadOnly.
Options
Optional. A Long value that indicates how the provider should
evaluate the Source argument if it represents something other than a
Command object, or that the Recordset should be restored from a file
where it was previously saved. Can be one or more CommandTypeEnum or
ExecuteOptionEnum values, which can be combined with a bitwise OR
operator
----------
GetChildren Method (ADO)
Returns a Recordset whose rows represent the children of a collection
Record.
Set recordset = record.GetChildren
Return Value
A Recordset object for which each row represents a child of the
current Record object. For example, the children of a Record that
represents a directory would be the files and subdirectories contained
within the parent directory
|
