Search results

Well, that's the question, really: Does a technique exist besides the obvious, of tinkering with coordinates and dimensions. Regarding controls, the anchor properties are all that are necessary here. Really, only the memo control need resize with the form and it already does. I would add it...

Colin, thanks. This is just the direction I'm headed, especially after George's and @MajP 's input. Simply because, to me, the additional window sizing options afforded in Windows 7 (I believe) by pressing Win or Win + Shift and an arrow key (maximize vertically, maximize horizontally, anchor...

LOL. Actually, the specific context is PopUp forms in single form view having a text box bound to a memo field. An unbound example would be a custom Zoom form, the chief purpose of which is to get more real estate for a memo-bound control. A bound example might be a data entry form, needing...

Yes, I neglected to mention that technique, but in the end it is simply another manner of setting Form.Top and Form.WindowHeight (and the method's other two parameters and the corresponding form properties), which I mentioned.

The thread title. Is there a way to maximize a form, meaning a PopUp form in my case but perhaps also a form if in overlapping forms mode, vertically? Put otherwise, is there a way to get or set this window state for such a form? By "vertically," I mean vertically-only, retaining the form's...

I haven't done a study, per se, but it is fairly easy. This nuance isn't something that most people would expect. Null handling is a bit arcane for beginners and it may not occur to them to think what the test is for whether "Required" is met. This is true. My statement was overly broad...

A default value differs from a blank value, to be clear. A default value follows from what's expressed in the field's DefaultValue property. Delete the "0" for numeric fields and the field will be Null for new records. AllowZLS doesn't set the default value of text fields to "", it just says...

I actually had been thinking along these lines and by experimenting with adding a null record to the lookup table. Alas, no dice. Agreed that 0 as default for numeric fields is inappropriate. I've gotten stung on this with FK fields a few times. Deleting the "0" from the field's DefaultValue...

Good thoughts and questions. Initially, this is more the "Loan Type" scenario you describe. Furthermore, the main table has no records at all. So, this isn't a question of it having records with FK values not matching those in the lookup table. Its FK field has AllowZLS = No, so that field...

That's true, of course, and is the case. No reason for the problem, even still. What ended up working was deleting the relationship another table had with the lookup table. I have no end of tables sharing a lookup table in other contexts, so this explains nothing. Re-creating this second...

I actually did say, actually: The main table has no records. So, any and every record will start with a null FK value because AllowZLS = No.

This is a new one. I'm encountering the error "You cannot add or change a record because a related record is required in table [X]". The first question is why would this be? In my experience, FK field values are optional, so this comes as a bit of a surprise. The second question is what can...

If I understand correctly, you're describing a library interface class implemented and instantiated by referencing projects' classes. My problem differs, I believe, because it involves the library calling code in the referencing (i.e., front-end) project. As I noted in response to another...

If I understand correctly, this still contemplates the front-end ribbon calling the library function. My problem is getting the library to call the front-end function. The library code in question is a framework of object wrappers sinking front-end object events. E.g., if I double-click on a...

The difficulty is that that table must exist in the referencing project or its back end because it is specific to it, and it would need to be visible to the library project's code in the same way.

VBA succeeds in boxing out the notion of an entry point other than a document in a COM app, in a variety of ways. One can get close by understanding event progression but even it has constraints. It is fairly liberal about passing objects, if not initializing them, and the object model...

Yes, of course, just for starters. I'll sacrifice orthodoxy for function but it seems to me this is the road to perdition. There is no difficulty in designing an object to accept parameters, however, including the identity of the referencing (or instantiating) object. Or, for that matter, to...

I've been refactoring a number of projects and migrating generalized code to a library ACCDB over time. It's gone practically without a hitch and many ACCDB projects reference it and instance its classes like a charm. As this refactoring has progressed, I have encountered one difficulty...

Colin, you're a font of knowledge. More than I can bite off on this instant but I've just bookmarked those of your pages I hadn't already. Among other things, the NavPane code addresses an item on my development plan. I've already settled on the SendKeys approach for A2007 contexts and had...

You're right about F11, my mistake. Ctrl + F1 is what does the trick. I'll edit my original post presently. I am actually working on 2007 for present purposes. Its ribbon implementation not being ready for prime time as you say explains much, not only the fact that the ExecuteMso method...