By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,641 Members | 2,110 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,641 IT Pros & Developers. It's quick & easy.

Ac 2007 Connections; preliminary look

P: n/a
Everything looks the same, SO FAR.

DAO is there and living and well.

ADO can be referenced and the default CurrentProject.Connection either
is an ADODB.Connectiion or can be coerced into an ADODB.Connection;
it's TypeName is returned as "Connection". It seems to have all the
ADODB Connection's Properties and Methods.

There is a new ADODB Provider:
viz,
Microsoft.ACE.OLEDB.12.0

This provider can be used beyond (outside) Access [something I inferred
from the blogs would NOT be]. This Windows Script works swimmingly.
<package>
<job identity=jobADOTest>
<?job debug='true'?>
<script language=jscript>
var c=new ActiveXObject('ADODB.Connection');
var r=new ActiveXObject('ADODB.Record');

c.Open('PROVIDER=Microsoft.ACE.OLEDB.12.0;DATA SOURCE=C:/Documents and
Settings/Lyle Fairfield/My Documents/Database1.accdb;PERSIST SECURITY
INFO=FALSE;Jet OLEDB:System database=C:\Documents and Settings\Lyle
Fairfield\Application Data\Microsoft\Access\System2.mdw')

r=c.Execute('SELECT * FROM Table1');
WScript.Echo(r.Fields(1).Value);
</script>
</job>
</package>

That's all folks. I'd be very interested to hear about others'
explorations into this area.

May 26 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.