-
Reposted 08/23/00
<html>
<p>
Attn parksie and jhausmann
About comparison table
</p>
<table>
<tr>
<td></td>
<td>DAO</td>
<td>RDO</td>
<td>ADO</td>
</tr>
<tr>
<td>Asynch queries</td>
<td>X</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Batch update and error handling</td>
<td>X</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>MaxRows property for queries</td>
<td>X</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>In/Out/Return value parms</td>
<td>X</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Return multiple recordsets</td>
<td>X</td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Disconnected recordsets</td>
<td></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Independently create objects</td> <td></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Queries as methods</td>
<td></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Efficient MDB file access</td>
<td>X</td>
<td></td>
<td></td>
</tr>
<tr>
<td>Fires notification events</td> <td></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Integration w/SQL debugger*</td>
<td></td>
<td>X</td>
<td>X</td>
</tr>
<tr>
<td>Free-threaded</td>
<td></td>
<td></td>
<td>X</td>
</tr>
</table>
<p>
*Hey, folks. That debugger is crap, i wouldn't even bother looking at it. Use access or oracle to test your sql.
-chuck
</p>
</html>
[Edited by Chuck Sweet on 08-23-2000 at 08:11 AM]
-
Cool, thanks. Although can you enclose it in code tags so that the X's line up...please?
-
Never mind, I looked at the page source. :)
-
Quote:
Originally posted by Chuck Sweet
Attn: parksie and jhausmann
Code:
About: comparison table
DAO RDO ADO
Asynch queries X X X
Batch update and
error handling X X X
MaxRows property
for queries X X X
In/Out/Return value
parms X X X
Return multiple
recordsets X X X
Disconnected
recordsets X X
Independently create
objects X X
Queries as methods X X
Efficient MDB file
access X
Fires notification
events X X
Integration w/SQL
debugger* X X
Free-threaded X
*Hey, folks. That debugger is crap, i wouldn't even bother looking at it. Use access or oracle to test your sql.
-chuck
the SQL "debugger" is intended to be used to aid debugging stored procedures and triggers, Access cannot help you there.
-
yeah, you're right (jhausmann) on that count. i work predominately with access so far, so i haven't had much occasion for stored procedures (yet). sorry about the format. i don't know anything about the 'code tags'. I tried html, but i don't think it worked.
chuck
-
I've never used stored procedures, but is it what I think it is? As in, can you do value comparisons and stuff like that? (then execute a specific piece of code)
-
Yeah, i think. essentially you can write a procedure (or function) for manipulating data and tables and stuff on the database side, so that instead of having to open a recordset or load a bunch of data, you send the command to the database to take care of certain redundant operations. if anyone following this thread knows any better, feel free to jump in here and do some correction.
chuck
-
Parksie, Yes. Another advantage is that the SQL is pre-compiled, ie, it executes faster.
-
So if you're doing a high-use system, it's a good feature to have...does Access support them, or would I need to move up to SQL Server / Oracle? (If I find them in mySQL that's just as good).
-
They do not exist in Access, I do not know about MySQL.
