Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / February 2006

Tip: Looking for answers? Try searching our database.

Exporting to a local path

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lorenzo - 10 Feb 2006 14:30 GMT
Hello there,
I have small application that I keep on my local machine but is sometimes
opened and used from another machine simpley by sharing the .mdb file to
another user.  I have no needs right now to have a more sofisticated
envirorment so I would like to keep things as they are.  I have a problem
though that I am having an hard time resolving:
I am programmatically exporting some access tables/queries from the db to
another database on the same machine and let's say for example in the same
directory where the sending mdb file resides.

This is my routine:
  DoCmd.TransferDatabase acExport, "Microsoft Access", _
   "G:\Documenti\Access\Online.mdb", acTable, "tblPrenotazioni", _
   "tblPrenotazioni"

It all works ok as long as I am working an my machine but clearly as I run
the same command from a different machine I get an error of object not
found.
I have tried using an absolute path such as \\COMPUTERNAME\PATH \FILE but
does not work.

Do you have an idea on how I can reference the file path from 2 different
machine?
Thanks for your help,
Lorenzo

Larry Linson - 11 Feb 2006 01:35 GMT
Well, the simplest approach is to let the user (who may, it seems, be
yourself) choose the destination using the Windows Common Dialog -- freely
usable code for that can be found at
http://www.mvps.org/access/api/api0001.htm.

Otherwise, you are likely to have to rely on no one ever changing the file
structure. That would mean, even, remembering not to do so yourself.

 Larry Linson
 Microsoft Access MVP

> Hello there,
> I have small application that I keep on my local machine but is sometimes
[quoted text clipped - 21 lines]
> Thanks for your help,
> Lorenzo
Lorenzo - 16 Feb 2006 10:20 GMT
Hello Larry,
thanks anyways for your help I have found a way that achieves the same
result but is more suitable for me:

Application.CurrentProject.Path & "\anyfile.mdb"

Thank you!
Lorenzo

> Well, the simplest approach is to let the user (who may, it seems, be
> yourself) choose the destination using the Windows Common Dialog -- freely
[quoted text clipped - 32 lines]
>> Thanks for your help,
>> Lorenzo
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.