Search results

I read Pat's post you referenced And it certainly can help with some of the issues with updating procedures "..The moment you have a BE change.." if the BE changes it's because the program code has changed it, via sql instructions, and therefore the reconnection of modified tables can be done...

Yes, of course we are talking about a project that uses Access as a development environment for forms/reports/code and a db server to hold the data "..since you have done this before.." If you tell me where I would have asked questions that do not concern Access I would be grateful I hope...

I understand what you mean, and I sincerely appreciate the time spent on the explanation above Which however does not affect the problem posed in the slightest So, let's say I want to start a project (I'm talking about forms/reports/code, the data is on a classic db server), which allows the...

This is not always possible Yes, this could be a reason

Yes of course mine was not an answer to your question You made a contrasting statement ("..If you seriously anticipate your project growing to more than..") with what I had already written before I wanted to point this out to you

I see that everyone refers to the programs they worked on and then says "..if I did this, then you can't do anything else.." It's a highly illogical way to proceed Maybe I'm asking for a technique/system that is normally never used with Access But this should stimulate your curiosity to find a...

No question is a waste of time, that's for sure It may be that the question does not admit of solutions, stating this would already solve the initial question My goal is to understand how to do something that I currently do not know how to do If you think that this is demonstrating my...

I think I've already answered this The final size is not known

The question has not changed The technical limits of the various versions of Access are perfectly clear and @Edgar_ reminded them in post #15 But the question asked does not concern the technical limits of Access Maybe I did not explain myself correctly, but the question asked is: - how to...

Where the question has changed???

There are technical limits for the development environment, in this case Access, beyond which you can not go My question is aimed at understanding how it is possible to create a project where, while working within the imposed limits, it is possible to increase the number of forms / reports /...

Thanks for sharing your experience But this does not contribute anything to the question posed initially Yes, user memory management can quickly become a problem, and so wanting to pre-view the possibility of monitoring, how to do it?

Maybe you didn't read the request well I asked: "..how do you 'set things' up from the beginning to allow this growth.." "..how to organize 'a project' to avoid it reaching dimensions incompatible.." I never asked how to work on a file exceeding the limits imposed by the environment you are...

I am very interested in the topic of communication between Vba and an opc server Where can I find the correct library?

What exactly is the purpose of all these considerations? I don't see any useful indication to clarify the question posed initially

You don't need to repeat it, it's perfectly clear And indicating the size of the largest file you've worked on is of no use in understanding how to deal with the problem I asked how to organize a project (also understood as a set of multiple Access files or similar) so that it can grow in size...

No, the final size is not known

The question is: how to organize a project to avoid it reaching dimensions incompatible with the limits of the development environment All other considerations are useless

This means that the project grows by adding new forms and reports and code, after being released.

Sometimes these are projects with a few dozen forms, tables, and some code modules But sometimes we are faced with projects that have hundreds of forms, hundreds of reports, dozens of modules even with a lot of code, and in this case we often get close to the limits of the Access environment...