OK, I'm bored. If you care to share anything concrete, maybe someone can ping me. Leaving for now.
Your choice is your choice is a good choice.
What kind of "anything concrete" you had expected?
Imb.
OK, I'm bored. If you care to share anything concrete, maybe someone can ping me. Leaving for now.
Hi Uncle Gizmo,Additionally, if you have a YouTube video or other visual demonstration of your system in action, sharing that could go a long way in illustrating its capabilities and encouraging constructive feedback from other developers.
Install OBS, it's free.and I don't know how to make a YouTube video presentation
I do not have any skills in making videos, but that is pretty much what I did here, using OBS.Install OBS, it's free.
Run it.
Add "display capture".
Click "start recording".
Show what you want to show.
Click "stop recording".
Go to youtube.
Click upload.
Choose the video you just recorded.
By default, the video is in your videos folder.
Done
Hi Pat,OK, I'm bored. If you care to share anything concrete, maybe someone can ping me. Leaving for now.
Hi Edgar_,Install OBS, it's free.
Run it.
Add "display capture".
Click "start recording".
Show what you want to show.
Click "stop recording".
Go to youtube.
Click upload.
Choose the video you just recorded.
By default, the video is in your videos folder.
Done.
Hi Pat,Why? If the client can run using the Access RunTime engine, there are far better versions of Access to settle on. Or, if you are having the client purchase ONE full copy so they can make design changes if they have to, 2010 and 2016 are far better options than 2007.
I too am anxious to see a form where you provide some kind of list selection without using combos or listboxes. I suppose you could use tiny subforms, but unless you've built your own com control, I don't know how else you could provide a picklist.
Preach on brother, preach on.Something I learned a LONG time ago is "One size DOES NOT fit all."
Because every company's data collection method and workflow is different.
Hi raziel3,It is customizable and not bloated and restrictive like many out of the box solutions which, from what the op described, is what @Imb is trying to achieve.
Hi Pat,
I start with a form to add a new person/relation. T
Hi Uncle Gizmo,Over 40 posts in this thread!!! ---- You don't appear to be able to convey your message very well.... In your last post you give the impression that it's everybody else's fault!!!!
Don't you think you should look closer to home???
Hi Edgar_,@Imb
I must confess I have no idea of what this thread is about, but based on the first few posts, it seems you're trying to get ideas or contributions that help you scale your currently 50MB+ code base. But instead of scaling your app, what scaled is the heat in this thread in terms of the skepticism towards the solution you're currently showing, which you say is a single form that morphs into controls and that this approach helps you maintain more than 100 applications that may or may not be different.
I am not scaling the code base, just to scale. The purpose is to add functionality and flexibility, whatever that is.Question 1:
Is the summary correct?
With regard to the above, "The form" (in fact I use two template forms, one for continuous overviews and one for all the rest) is tuned in detail in the Open event of the form, through generalized code blocks, and these can be shared. The controls are already there, but must be "activated". An additional advantage is that you can create in memory all kind of form-representations to suit any situation.Question 2:
What are you actually doing? Are those textboxes being created on the fly or are they becoming visible?
In the separate applications I have no "hard-coded" forms, but only modules with generalized building blocks.Question 3:
How does this approach actually help you maintain many applications?
That is only necessary if you have many static forms, that must handle the different types of control per form. In principle I have one "fluffy" form.Question 4:
Did you even try to use classes to build your forms?
That is the point I want to clarify: that it is also possible in Access, with a different look towards forms.Question 5:
Do you know other technologies, like HTML or WPF, do this by default and are arguably much easier to write than making this work with Access?
I really wish that were the case!Thanks to your questions, I have - finally - got the opportunity to clarify a little more what this concept means.