Copy access objects (reports, queries, etc) from one Access db to another using VB.net

  • Thread starter Thread starter kenbeard
  • Start date Start date
K

kenbeard

Has anyone seen anything or have an idea of how i could copy an Access
object (queries, reports, etc) from one db file to another. I would prefer
to use VB.net but I'm open for other suggestions, but it we need NO user
interaction.

Or maybe even a way to use one Access db (front end) to create a query,
report but behind the scenes have it save to another mdb file (back end).
What I've created is the ability to allow users to create custom queries and
reports without the need to open the backend file then import, etc. But I
want to upgrade the front end by replacing it entirely but this (since the
objects of the user created type are stored in the front end) would be lost.

Any ideas, code, etc.

THANKS!!!

Ken
 
Hi kenbeard,

Thanks for posting in the community.

Currently I am looking for somebody who could help you on it. We will reply
here with more information as soon as possible.
If you have any more concerns on it, please feel free to post here.


Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
 
Sounds good, I'll keep my eye on the newsgroup. I look forward to your
suggestions.THANKS

Ken
 
Hello Ken,

Thanks for your post. As I understand, you want to programmatically
export/import Access objects between one Access database (.mdb) and another
database. Please correct me if there is any misunderstanding. I now share
the following information with you:

Generally speaking, we can manipulate .MDB by using ADO .NET or Automation
in VB .NET. As in this case, you should use Automation since it requires
Access application-specific features. Please refer to the following MSDN
article on Access Automation:

HOW TO: Automate Microsoft Access From Visual Basic .NET
http://support.microsoft.com/?id=317113

After further investigation, I suggest that you can use
DoCmd.TransferDatabase action to export/import Access objects in your
automation application. Please refer to Microsoft Office Access Help for
detailed information on this command.

BTW, in the future, it would be best to post these questions in the
following newsgroup:
microsoft.public.access and its sub groups.

Please feel free to let me know if you

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi Ken,

I would like to follow up on this issue and see if any progress has been
made. I haven't heard from you in 2 days, were you able to check my reply?
Should you have any questions, please feel free to post here.

Looking forward to your reply!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
oh, thanks for the follow up....I was actually working out everything. I
read that site and I think that's what I'll do. I wasn't going to say
anything about posting in this newsgroup but since I'm responding I might as
well explain. The only reason I posted under the framework and not the
Access board was because I didn't think the Access board was a "Managed" and
since I have a universal MSDN license and I wanted to use the framework (as
much as possible) I choose to use this board. Plus I don't like to double
post so I posted here first. Since I got what I needed I didn't repost
under the Access board.

My only question that does come to mind (and I haven't tested it, so maybe
you might know) is I have users using Microsoft Access 2000, 2002, & 2003.
The database files are 2000. If I build the app to use a reference to 2002
will it still work if the end user only has 2000 or 2003 installed? Since I
reference Access using COM and it creates interop files the actual Access
dll used is on the client system (right?) then my app wouldn't find
"Microsoft Access 10.0 Object Library" (Access 2002) if the client has 2000
or 2003 installed.

As always THANKS for any and all advice you can give, in addition, let me
reiterate my thanks for the follow up.

Ken
 
Hello Ken,

Thanks a lot for your feedback. As to the question regarding multiple
version of Access, I recommend that you'd better build the app to use a
reference to 2000, because Office applications provide backward
compatibility. Please refer to the following KB article:

INFO: Writing Automation Clients for Multiple Office Versions
http://support.microsoft.com/?id=244167

Hope this helps.

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Sounds like a plan...I didn't think about the backwards compability. Once
again THANKS for the advice.

Ken
 
Back
Top