Search results

  1. C

    Access instance remains in memory once closed

    I've done some more testing - in a win10 VM I have 365, 64bit office which was on a fairly old version (2412 Build 18324.20194) and the code ran as expected - the access instance is removed - takes 2-3 seconds. I upgraded to the latest version (2508 Build 19127.20154) and the code still works...
  2. C

    Query optimization: Why does Access use temporary index instead of index or rushmore for a JOIN query with SUM?

    just curious- what affect on the jet plan (if any) if you reversed the join as above and grouped on the other table?
  3. C

    Relationships for standard & special rates

    was about to say the same thing, you need an effective from date field and possibly an effective to date field if you do limited time offers. And with regards old prices, be careful with credits - price sold at £100, a bit later price is increased to £110. If you want to credit back after the...
  4. C

    To Merge or Not To Merge... Backends

    If each of your FE’s do not share data with other FE’s there is no real benefit in merging the back ends. You might hit a max db size or number of connections. On the other hand it might be easier to maintain
  5. C

    Access instance remains in memory once closed

    I do have an add-in - but pretty sure Colin will as well. However I really don't want to remove it and reinstate as a normal process. I'll see if I can do it once to verify. Ditto anti-virus. Do you have add-in's? if not, perhaps you can try the code, see what you get?
  6. C

    Access instance remains in memory once closed

    No - I have a new machine on win 11 with 365. Still have it in a virtual machine I ported over from my old machine - I can take a look later
  7. C

    Access instance remains in memory once closed

    Using Colin's code (with the exception of the target file which does not have autoexec or a specified startform) I still get the problem - see the attached video which shows step by step by step what happens in task manager on execution of each line. Note the comment on set app=nothing needs...
  8. C

    Access instance remains in memory once closed

    OK - I've done some more testing and tried Colin's code - but still hit the same issue - basically app.quit doesn't appear to do anything and it locks up on Set app=nothing until I manually end task in task manager. Summary of events when stepping through the code: Set app = New...
  9. C

    Access instance remains in memory once closed

    Thanks for the replies - I’m out and about until late, so will reply tomorrow after more testing
  10. C

    Access instance remains in memory once closed

    Thanks for the responses My understanding is the difference between ..AS New and createObject is AS is early binding and creatobject is late binding. However I have tried both ways with the same result, regardless of how accApp is declared. To go back to the simplest test try this code change...
  11. C

    Access instance remains in memory once closed

    I have an app which creates an Access instance and populates it with another db that the user selects for analysis. Even if I do nothing and then close the instance it remains in memory. It was reported as a bug about 3 years ago (although that seems to be more about closing access in general...
  12. C

    Re-design a wellworking data base

    Might be talking at cross purposes but with terminal server and Remote Desktop the only thing traversing the WAN is mouse and keyboard events one way and screen refreshes the other. All transactions are handled on the server/remote device. So performance is high.
  13. C

    Future of Access

    Seems to me you are arguing about the difference between a bus and a train. Both transport people and each have their own advantages and disadvantages. Which one you use depends on what matters to you. And sometimes you don’t have a choice. If you don’t want to use the train because it doesn’t...
  14. C

    Re-design a wellworking data base

    with regards moving to sql server/azure (or mySQL or any other rdbms), take a look at this thread. The reasons for upsizing are different, but the things to review remain the same https://www.access-programmers.co.uk/forums/threads/addressing-performance-issues.291269
  15. C

    Re-design a wellworking data base

    To clarify- you have an access backend with all the tables in a shared location on a server together with all the related pdfs, jpgs etc. and each user has a front end accdb on their local machine which links to the backend? It comes down to data security, licensing costs, time and cost to...
  16. C

    Re-design a wellworking data base

    not sure if sql server express can be installed on a terminal server, but if it could you would have the benefit of speed, greater data storage and improved data security (subject to how secure your front end is in the first place)
  17. C

    Re-design a wellworking data base

    Depends on the number of users and therefore licensing costs by I would suggest using terminal server. Each user has a login and a profile. Put the back end in a shared folder and a copy of the front in each users profile and relink to the newly located backend. You can install runtime access...
  18. C

    Solved Begginer! please help.

    Agree data should not be deleted but you will probably need a ‘termination’ field for when a client or vet leaves the practice, a pet dies, a vaccine is no longer available etc. usually a date field (where null means current) perhaps with a second text field to indicate why
  19. C

    Form on form

    they don't need to be linked to a table, there is noting to bind them - just leave the subform control linkchild/master properties blank easy to do, in design view of your main form, just drag the forms you want from the navigation window and size to suit. You may want to delete the associated...
Back
Top Bottom