Re: Modify Forms in Separate MDB

From: solex (solex_at_nowhere.com)
Date: 06/07/04

  • Next message: anonymous_at_discussions.microsoft.com: "CreateFieldMethod" 
    Date: Mon, 7 Jun 2004 16:22:51 -0400

    Jason,

    Now that I understand your reasoning, I would suggest you begin to look for
    another solution for your front end application.

    I have used the Dot Net no-touch deployment system with great success. If
    each of your clients has an IIS Webserver you could distribute the updates
    to each of their IT departments. They could test the new version and simply
    place it on their web server when they have completed their QA. The cool
    thing is that the applcation can be updated any time and the next time the
    user starts the application they will automatically get the updates.

    The down side is that (a) your application must be created so it can be
    distributed via XCOPY and (b) thier web server must always be up.

    The other solution is to create a web interface, but you know the ups /
    downs with that approach.

    Good Luck,
    Dan

    "Jason E" <anonymous@discussions.microsoft.com> wrote in message
    news:192be01c44cc9$0d86ebe0$a301280a@phx.gbl...
    > There are a few issues - most of them related to the
    > conservative nature of the client - wanting to be very
    > sure new versions do not interrupt the use of the product.
    >
    > Reasons the client does not want to send out new versions
    > very often:
    > - Hard to communicate/force all site to comply with
    > implementing new version
    > - Each implementation has chosen their own installation
    > location for front and backend MDB's, so some concern
    > with sites getting the attachment to their backends
    > correct.
    > - There is some user/site specific data in the front
    > end, so need to get that info into the new front end
    > - Auditors and IT group demand extensive testing of new
    > releases, so time and money are a factor.
    >
    > Back to the original question - do you know of any way to
    > programmatically change forms in one MDB from another MDB?
    >
    > Thanks
    >
    > >-----Original Message-----
    > >I do not see your problem, if the database and app are
    > separated what is the
    > >big deal with sending out a compiled MDE file for the
    > application? There is
    > >no install just overwrite the existing copy. BTW and
    > MDB file is not
    > >compiled
    > >
    > >
    > >"Jason E" <anonymous@discussions.microsoft.com> wrote in
    > message
    > >news:194c001c44cc4$5389fe70$a501280a@phx.gbl...
    > >> I meant that the changes I want to make (changing the
    > >> size and location of controls on a form) I would not
    > >> expect to lose the compiled state of the MDB.
    > >>
    > >> By distributed I mean that it is in use in several
    > >> hundred locations worldwide. It is also a critical app
    > >> for the client. This is why the client would prefer not
    > >> to force these hundreds of users to run an "install"
    > >> procedure.
    > >>
    > >> We have created new installs in the past, but were
    > hoping
    > >> to avoid the more significant development and testing
    > >> involved in that and find a way to make some minor mods
    > >> to the existing MDB's.
    > >>
    > >> The database and app are separated. We have
    > recommended
    > >> using MDE, but so far the client is resisting the
    > change.
    > >>
    > >> Thanks
    > >>
    > >> Jason
    > >> >-----Original Message-----
    > >> >What does this mean: "The modifications should not
    > >> impact the compiled state
    > >> >of the MDB."? Also what does it mean to have a
    > >> distributed MDB?
    > >> >
    > >> >Your best bet is to separate the database and the
    > >> application into two
    > >> >separate MDB files. Compile the application to an MDE
    > >> and distribute the
    > >> >MDE. Any new changes would involve distributing the
    > MDE
    > >> file.
    > >> >
    > >> >Dan
    > >> >
    > >> >"Jason E" <anonymous@discussions.microsoft.com> wrote
    > in
    > >> message
    > >> >news:193b901c44cba$f0836ef0$a401280a@phx.gbl...
    > >> >> I have a distributed MDB that I would like to modify
    > >> >> programmatically rather than sending out a whole new
    > >> MDB
    > >> >> to replace it.
    > >> >>
    > >> >> What I would like to do have users open a separate
    > MDB
    > >> >> and run code which opens the MDB to be changed and
    > >> >> modifies the layouts of some forms and reports. The
    > >> >> modifications should not impact the compiled state
    > of
    > >> the
    > >> >> MDB.
    > >> >>
    > >> >> It seems that you can modify another MDB's tables
    > and
    > >> >> queries programmatically, but I can't find a way to
    > get
    > >> >> to its Forms or Reports to modify them.
    > >> >>
    > >> >> Is there any way to do this?
    > >> >>
    > >> >> Thanks
    > >> >>
    > >> >> Jason
    > >> >
    > >> >
    > >> >.
    > >> >
    > >
    > >
    > >.
    > >

  • Next message: anonymous_at_discussions.microsoft.com: "CreateFieldMethod"

    Relevant Pages

    • Re: Can it be that NO ONE HERE knows this answer?
      ... Sounds like you want MDE code (which I presume you control the source code ... otherwise you may want to forget it) to insert/update/delete an MDB ... then would need to build a .net client side application to talk to the web ... possible to link a client side MDE with a WEB server MDB table using ...
      (comp.databases.ms-access)
    • Re: Can I link to an mdb in a Web Folder?
      ... > I'm trying to link a remote client Access app ... > to an mdb in a web folder on my web server. ... > readOnly access to the web folder mdb, ...
      (comp.databases.ms-access)
    • Can I link to an mdb in a Web Folder?
      ... readOnly access to the web folder mdb, which itself links to SQL Server ... I have succesfully created a WebDAV on our Win2003 Server web server ... Win2000 test client pc) which points to the web folder on the web site. ...
      (comp.databases.ms-access)
    • updateable query
      ... Wenn ich die Anwendung vom Client aus starte funktioniert auch alles ... solange ich keinen Insert oder Update auf die MDB ... das bin-Verzeichnis zu berechtigen, ... Next by Date: ...
      (microsoft.public.de.inetserver.iis.asp)
    • Merge replicating a JET backend
      ... We have a large legacy application built in MS Access (front-end client mdb ... with back-end shared data mdb) and are looking for a good migration path ... To me the ideal path would require that we be able to use SQL server merge ...
      (microsoft.public.sqlserver.replication)
    Loading