Search results

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

Yes, using external libraries is a possibilityIf the technical limitations of a single Access file can be increased by adopting external libraries then this could be an avenue to experiment with The ribbon indicates the possibility of connecting data from an external db, and this is already the...

I don't understand what you mean If you explain me i would be grateful

I'm not talking about library files I'm talking about any project that can be built with most other code development environments Where exactly did you read that I would suggest using library files?

1- I'm not STARTING development I'm trying to figure out how to evolve projects that are approaching the technical limits of a single Access file 2- Project ownership or who pay for it doesn't matter on the technical issue

No, actually when you work with Microsoft Access, you USUALLY work with a single file that contains everything The same thing is not true with all the other development environments, just look at a Delphi or Visual Studio project or a Php or Android Studio or RubyOnRail project They are always...

If a single Access file has technical limitations, then we use multiple Access files It can be a way to overcome the limitations imposed on the single file If a single Access file can 'hold' a maximum of 1000 forms then perhaps two Access files can 'hold' a maximum of 2000 forms and so on What...

"..how large your project is.." The maximum project size can be defined with extreme precision The project must be able to contain X+1 objects Where X is the maximum number of objects that can be managed by a single Access file When this problem is solved, any growth can be supported "..do...