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 / September 2003

Tip: Looking for answers? Try searching our database.

Network Connection lost

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Karen Hagerman - 11 Sep 2003 18:43 GMT
I have delivered a small Access database.  The backend is on a network file server (Novell network).  Each user has a copy of the same front end with the forms and reports.

When bugs are discovered I need to rework forms and send them to the client so they can update their client applications.  I have tried to send a separate update database which only contains the updated forms and associated VBA files.  When we export the forms from the update db to the client front end db's, they get a 'network connection' error of some sort.  Bottom line is that the only way to update the forms is to supply a new front end db each and every time.

I have tried deleting the subject forms in the current db and then exporting from the update db with the same error.

This may not be the right newsgroup to post and I'll post elsewhere if necessary but 1)  is this a familiar problem to anyone? and/or 2) is there a better way to update the forms?

Karen
Rick Collard - 11 Sep 2003 20:24 GMT
Instead of pushing the updated objects from the update database into
the front end try it from the other direction.  Add an option to your
front end that drives the update and pulls any updated objects from
the update database.  Of course, you need to delete the object before
importing to keep the same object name.  We have been distributing
product updates this way for some time without any problems.  If
memory serves, beginning with Access 97 you had to do it this way.  I
am not sure about the error you are getting but give this approach a
try.  HTH

Rick Collard
www.msc-lims.com

>I have delivered a small Access database.  The backend is on a network =
>file server (Novell network).  Each user has a copy of the same front =
[quoted text clipped - 16 lines]
>
>Karen
Karen Hagerman - 11 Sep 2003 23:49 GMT
Thanks Rick but is that function of the database or do I have to write
separate VBA for that functionality?

Karen

> Instead of pushing the updated objects from the update database into
> the front end try it from the other direction.  Add an option to your
[quoted text clipped - 29 lines]
> >
> >Karen
Rick Collard - 12 Sep 2003 03:03 GMT
I have heard of replication used for this purpose but I am not
familiar with that approach.  I developed our version update process
using VBA and a form and table or two to drive the process.

Rick Collard
www.msc-lims.com

>Thanks Rick but is that function of the database or do I have to write
>separate VBA for that functionality?
>
>Karen
Karen Hagerman - 12 Sep 2003 20:24 GMT
Thanks,

I'll write some VBA!

Karen

> I have heard of replication used for this purpose but I am not
> familiar with that approach.  I developed our version update process
[quoted text clipped - 7 lines]
> >
> >Karen
Ed Ardzinski - 11 Sep 2003 20:26 GMT
Are using an mde or mdb as the front end?  Although I have
been able to move things into an MDE I don;t think forms
is an object type you can import in...
Karen Hagerman - 11 Sep 2003 23:50 GMT
Hi Ed,

The front end is mdb, the back end is mde.

Karen

> Are using an mde or mdb as the front end?  Although I have
> been able to move things into an MDE I don;t think forms
> is an object type you can import in...
Albert D. Kallal - 14 Sep 2003 01:53 GMT
Well, of course you have to use the linked table manager to re-link to the
location of where the back end data file is. How is the front end going to
know where they placed the back end? It can't read their minds!

So, when they receive the file, someone there will have to use the linked
table manager and re-link to the back end. This should be done at client
site, and you can relink the one copy, and then distribute that to each user
(to save the trouble of each user having to re-link).

Unfortunately, you can't pre-link the location of the back end in the front
part unless you have an identical setup, and have the exact same path name
for the back end that the company is using.

You can (and should) however test if the connection fails, and then offer
the user a chance to re-link. That is normally what is done.

If you don't want your users to learn, or have to re-link using the built in
linked table manager, then you can roll your own code. There is some example
code on how to re-link tables at:

http://www.mvps.org/access/tables/tbl0009.htm

Also, to automatically have each user "update" the front end, you can use:

http://www.granite.ab.ca/access/autofe.htm

--
Albert D. Kallal     (MVP)
Edmonton,  Alberta Canada
kallal@msn.com
http://www.attcanada.net/~kallal.msn
 
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.