Search results

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

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?

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

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...

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...

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

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...

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...

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.

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...

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

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...

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)

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...

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

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...

personally I use the standard ISO format of yyyy-mm-dd in queries to avoid any possible confusion. Also, some rdbms/systems will distinguish between M and m and D and d (uppercase are long dates and the lower case short date) although should not an issue for Access which is not case sensitive

the code converts the date, a numeric datatype to a string. Not tested by I suspect the datepicker doesn't like strings - your error message says it all. And hopefully these controls are unbound otherwise you are mixing datatypes. But why need to code anyway? why not just set the format property...

sounds like the background form just needs the buttons and 3 subforms

I created this text file which I'm guessing is something like your xyz file 11 C -0.180226841 0.360945118 -1.120304970 C -0.180226841 1.559292118 -0.407860970 C...