Search results

"..forum's online scores.." What is this thing here? Is there anyone who gives us points? The scope has not changed 1- Yes, the "development environment" is Access.exe 2- Yes, Access.exe works with a single file at a time 3- And for a single Access file there are maximum limits to the...

It is a developer who has created a procedure that can be found with the name vcs-access and that allows the export of all the objects contained within an Access file to a text file, and the corresponding import to recreate the original project The procedure for dividing a single-file project...

Yes of course, this does not mean that I have one super-large project But this consideration has no importance in order to solve the problem posed I could actually have the problem to solve, or I could not have it, this thing has no importance in order to solve the problem posed Which honestly...

The fact that you worked on a project consisting of a single 70 Mbyte form/report/code file, does not mean that there cannot be projects of larger dimensions

No the problem has not changed Perhaps those who read the word 'project' immediately thought (this is because usually the Access developers work on a single file) to a single Access file But already from post9 it was expressly indicated that a 'project' is to be understood as composed of one or...

No, is a true project Million of records not impact on the question posed, the data db is external to the application You write of 'biggest database with thousand of object' Can you indicate how many forms, reports, modules this application is composed of? Does it work on Access 32bit or 64bit?

So far it seems to me that, assuming you want to create a large-form-report-code-project system, the main problems are two: - the limits on the number of objects that can be managed within a single Access file - the limits of memory that a single Access file can use In particular on the second...

No, seeing the future would be nice (but not that much) but it's not possible It is enough for me to understand how to organize things to obtain a project that can manage X+1 objects, where X is the maximum number of objects that a single Access file can manage I think it is the word 'project'...

I have provided those links for the sole purpose of making it clear that other experts on these topics expressly indicate that the 64bit version of Access/Office does not suffer from the memory shortage problem, but only the 32bit version does And this contrasts with the answer you gave me in post66

Yes, if we were in a group that discusses philosophy then we could write about why But we are in a technical group, and so I think it is enough to explain the how/what

This is the initial post "...The question is: working on a project that is expected to grow continuously at the rate of a few dozen objects/month, how do you set things up from the beginning to allow this growth without preventing the correct overall functioning?..." Nothing has changed at all...

Remembering all the work you've done isn't much help in solving this specific problem And even needing to understand what a software procedure actually does, from the developer's point of view, is completely useless Or if you like to think of a specific system, then think of a system that can be...

Knowing the features that the project will have is of no importance in finding a technical solution that allows the user to use a system with a number of objects greater than those allowed by the development environment. But what does the maintenance person who touches the accounting have to do...

They might not be 1000 But I would like to understand how to do if they were X+1 forms Where X is the maximum number of forms that a single Access file can contain

Thanks for sharing your valuable experience and knowledge Looking for information on the topic of memory management, I see that several experts (Karl, Mike, Daniel,...) seem to assert that Access 64bit is not affected by the problem of 2-4 Gbyte of memory to contain applications and data Is...

As long as there is someone who dares to post dead horses, any 3d can be derailed It can't be clearer than this If I had a solution, I would not have posted the request :)

The two (or three or more) tasks do not have to communicate with each other, they communicate with the db server Is there a maximum limit of 2Gbyte of usable memory also for the 64bit versions of Access? Do you know where I can find documentation that describes these things?

It seems like a Woody Allen joke, which notoriously doesn't make anyone laugh It's strange how administrators allow posts offensive of this type But maybe they haven't seen it yet

I think I asked this in this thread, what would be the point of opening another one? I have already written several times that the data is in an external db server And therefore this consideration has NO relevance for the solution to the problem posed Yes, this is a viable path, if a single...

"..get close to the limits of the Access environment.." post1 "..also understood as a set of multiple Access files.." post9 "..development environment, in this case Access,.." post18 "..various versions of Access are.." post23 "..that is normally never used with Access.." post33 "..that uses...