|
No ... you can probably do what you want, but not the way you describe it.
Access has a featured called "linked tables," which you want to get real comfortable with. Basically, even in a mdb file ( where the data lives in Access ) you can store individual pointers to other data sources with all the info the db engine needs to read/write data from them.
You can use ODBC here, so I'm assuming JDBC is an option, although I haven't tried it. Every time you open a "linked" table ( that includes any kind of query ) Access will open a connection to the data store, and get you a refreshed copy of the data.
So ... the answer is to create a linked table ( or several ) in MS Access, then design the report against your linked tables, or a SQL query that involves them. This way you don't have to do any ADO/RecordSet programming, don't have to write any insert statements, or really do much of anything out of the ordinary. Just build the table links, then use a normal select query in your report.
|
