It's been suggested over and over. But OP is not used to listen to others.You can probably achieve this with dedicated front ends for specific areas of the business
It's been suggested over and over. But OP is not used to listen to others.You can probably achieve this with dedicated front ends for specific areas of the business
You can probably achieve this with dedicated front ends for specific areas of the business which only contain objects relevant to that area.
At last. An actual description of the mythical Unicorn project.
Absolute worst case you'll possibly need 2 or 3 different front ends, connected to a single proper DBMS.
Only taken the thick end of 100 posts for you to actually write something that made sense.
It's been suggested over and over. But OP is not used to listen to others.
The actual limits have been stated in the early part of this thread but there is a limit of 32767 objects - forms/report/modules and controls for example. A typical form would have say 100 controls (many will only have 20 or 30) so just looking at forms with an average of 100 controls each, you would be limited to 324 forms - at the lower number of controls, perhaps 1500.
There is also a limit of 1000 modules - which includes forms with code - so if all your forms had code you would be limited to 1000 forms.
At 35 new forms a month (the OP's stated expectation), you've got between 10 and 42 months before you start hitting the limit.
All experts are getting nervous here, but I'm really enjoying it.if other answer to the question
I would like to thing you are capable of doing that yourselfThe counting ("..you've got between 10 and 42 months..") needs to be redone
Form with moduless are actually 634
Report with modules are actually 299
Modules of code are actually 109
provide the source for your figuresAlready now they do not appear to be those described in the Microsoft documentation
Yes sure, the sum is 1042, i can do it up to three figuresI would like to thing you are capable of doing that yourself
provide the source for your figures
...
There is also a limit of 1000 modules - which includes forms with code - so if all your forms had code you would be limited to 1000 forms.
...
For the purposes of solving the problem described it was not necessary to explain the specific case
OP is used to listen to other, if other answer to the question
Form with moduless are actually 634
Report with modules are actually 299
Modules of code are actually 109
The counting ("..you've got between 10 and 42 months..") needs to be redone
Sorry but maybe I explained myself badlyPlease provide the link to where I said
Form with moduless are actually 634
Report with modules are actually 299
Modules of code are actually 109
NoAmazing!
Are many of those forms automatically generated
Invoices, items, prices, the usual thingsCan I ask what sort of things they do? Are there lots of forms created just to get the user to answer a question or confirm something?
It grew like this because new features were added to an initial minimal coreStill genuinely interested to understand how it's grown so much. And especially why you need to keep adding forms at a rate of dozens per month!
Still genuinely interested to understand how it's grown so much. And especially why you need to keep adding forms at a rate of dozens per month!
are clearly written to try and demonstrate some form of superior intellect, when actually, all they are doing is reinforcing that he (the OP) has no real desire to comprehend the myriad of advice given or is simply too dim to understand it.For the purposes of solving the problem described it was not necessary to explain the specific case
It sounds a bit like there might be lots of highly bespoke forms for very specific purposes.now I'm trying to understand how to organize things a little better
If only you had written this to start with we would have known exactly what you wanted to find out.No
Invoices, items, prices, the usual things
It grew like this because new features were added to an initial minimal core
And having to add more, now I'm trying to understand how to organize things a little better
You can only create a finite amount of objects on forms, including any that are deleted.If that's the case, it should be possible to create forms that dynamically alter themselves that can be re-used for multiple purposes. If that's true you might be able to delete hundreds of them.
are clearly written to try and demonstrate some form of superior intellect, when actually, all they are doing is reinforcing that he (the OP) has no real desire to comprehend the myriad of advice given or is simply too dim to understand it.
Any time I want to show my user some data or pick something from a list I do it dynamically with a universal form. (Not created on the fly - it already exists - you just alter the text and the source query etc etc.)You can only create a finite amount of objects on forms, including any that are deleted.
This is therefore not recommended under any circumstances, in addition you can't make design changes in a compiled ACCDE version of any Access application, so "on the Fly" changes are a no-no.
You can understand exactly what I wanted by reading post1If only you had written this to start with we would have known exactly what you wanted to find out.