Results 1 to 15 of 15
  1. #1
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Front-end/Back-end combination strange behaviour (2003)

    I have three files: two front-ends(ScalveIng.mdb and ScalveSala.mdb) which connect to a back-end(Scalve_b.mdb).
    I put ScalveSala.mdb and Scalve_b.mdb in the same folder(c:valdiscalve) on the same pc while I put ScalveIng.mdb on another pc and connect it to Scalve_b.mdb via a local area network.
    The strange thing that happens is that, if you first open ScalveSala.mdb and then try to open ScalveIng.mdb, ScalveIng.mdb won

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Please remove the reference to OWC11 and reduce the files in size.

  3. #3
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Hi Hans, thanks for coming to the rescue. Sorry about the reference to OWC11 <img src=/S/blush.gif border=0 alt=blush width=15 height=15>.
    I've whittled the zip down to 1.8MB and you can still find it here as ScalveSala.zip

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    After re-linking the linked tables to the backend, I can open the front end databases in either order without problems (assuming that a message in Italian about a missing record is "normal").

  5. #5
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Thank you Hans, yes the message about the missing record isn't of concern in this instance. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>
    Is at least one of the front-ends connected via a LAN?

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    I'm at home, with only a single computer to work on. But I don't think that placing the frontends on a network drive would make a difference, since you mention that both frontends are installed in the same folder..

  7. #7
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Thank you Hans, you see, it's really fundamental that ScalveIng.mdb be connected via LAN(in my opening post I said, "I put ScalveIng.mdb on another pc and connect it to Scalve_b.mdb via a local area network.") because that's what causes the problem. Do you have any chance tomorrow to test it over a LAN?

  8. #8
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    I can only store one or more of the databases on a network share. I don't have access to other PCs in the network.

  9. #9
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    I'd be grateful if you can try putting the back-end on the network share and see what happens. Obviously the best would be to put ScalveIng.mdb on a different pc but it's better than nothing <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  10. #10
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Giorgio,

    I have tried it with the backend on a local drive and the frontends on the network, the backend on the network and the frontends on a local drive, and with all database on the network. No problems each time.

    I did notice one oddity. I obviously had to relink the tables in both frontends, using Tools | Database Utilities | Linked Table Manager. Normally, you need to specify the backend database obly once, but for one of the frontends (I think ScalveIng), I had to specify it for each linked table separately. So perhaps there is a problem with the links. Try relinking the tables in both frontends using the Linked Table Manager, and if that doesn't help, delete the linked tables and use File | Get External Data | Link Tables... to create the links from scratch.

  11. #11
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Thank you Hans, I had noticed that oddity too. I've followed your advice and tried both relinking the tables in both frontends using the Linked Table Manager and deleting the linked tables and using File | Get External Data | Link Tables... to create the links from scratch but the problem still remains and that is due to the fact that for some unknown reason the routine associated with the Open event in the startup form(Scalve) in ScalveIng.mdb executes instantly if ScalveSala.mdb isn't open while it takes 90 seconds if ScalveSala.mdb is open. So actually after 90 seconds ScalveIng.mdb does open.

  12. #12
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    That is quite long. A delay is to be expected because a lot of security checking goes on if a database is already open, but on my PC it's still only 7 seconds or so. I can't explain why it takes 90 seconds on your PC.

  13. #13
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Thank you very much my friend.
    <img src=/S/lex.gif border=0 alt=lex width=16 height=16>"Good things come to those who wait" <img src=/S/whisper.gif border=0 alt=whisper width=29 height=17>
    <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

  14. #14
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Giorgio,

    I think I have found a solution for opening ScalveIng when ScalveSala is open.
    What I have done is the following:
    I add a new form. Nothing special about this form. I used a continuous form based on the table fermi.
    At the beginning of the On Open event of the form Scalve, I add a line to open this form, hidden.
    Result : an instantly opening of the form Scalve even when ScalveSala is open.

    Can you test this on your network and let me know if it works for you too ?

    More speed tricks can be found at Microsoft Access Performance FAQ
    This case was found under the link : LDB locking which a persistent recordset connection fixes

    Best regards,

    Francois.
    Francois

  15. #15
    Bronze Lounger
    Join Date
    Jan 2001
    Location
    Alzano Lombardo, Italy
    Posts
    1,483
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Front-end/Back-end combination strange behaviour (2003)

    Works like a charm. Thank you Francois!!! <img src=/S/clapping.gif border=0 alt=clapping width=19 height=23> <img src=/S/cloud9.gif border=0 alt=cloud9 width=25 height=23>
    I had thought, without knowing anything about LDB locking, of using a
    similar stratagem by employing a basic, popup, modal form to
    be opened on startup with a timer to fire the opening of the Scalve form
    after a 30 seconds delay but the only result was to still wait an
    additional 90 seconds after the 30 seconds delay. <img src=/S/bummer.gif border=0 alt=bummer width=15 height=15>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •