Search results

That's a forum issue. The name is spelled correctly. I've never used the debugger in Windows. The excel spreadsheet opens correctly so I'm assuming the problem is with the reference to the control

Please bare with me on this. I am usinging Access 2003. I apoligize for asking this again but .. I did this right once before but I had to redesign the form. Somehow this has got messed up. I am using the syntax I have seen in Bob Larson's post on this. I am using a command button...

I discovered the reason for the locking was some code that I had forgotten to delete when I deleted the form to redesign it. The question I have now - is why don't the disabled fields show up disabled? My other question is- how do you reference a control on a linked subform from the main form...

At least now I have figured out why the fields are locked - I found some code that I had not deleted when I deleted the original form (rewriting this question clued me in to that). But I still don't understand why the fields are not disabled when the sub(linked) form is opened.

"As Uncle Gizmo has suggested, there really is no form/linked form construct in Access, other than a main form with a subform embedded in it. Calling/opening one form from another form, if that's what you're talking about, does not create a form/linked form." (quote from Missinglink) Perhaps...

Could someone please take a look at this?

The surprise is not the help menu - but that it is actually useful! Normally help-menus associated with Microsoft products are something of an oxy-moron!:D

Access 2003 user. On my report is the string 8959-19 (DAAD/wd) I am using DAADFILENUM: " 8959-19 (DAAD/" & [CompletedBy] & ")" Which works, but how can I make [CompletedBy] lower case? I tried < in the format of the text box, but the whole textbox becomes lower case, not just the...

Don't the images explain things?

(I thought the quote was "Lucy - you've got a lot of splaining to do!" If there are no "linked forms" what is this wizard doing? (see jpeg). The second form logically behaves exactly like a subform but it is physically separated from the main form. That is what I mean by "linked form" That...

I had originally designed the form/subform with the form wizard. I used the form wizard to create a form/linked form. I didn't physically separate the two.

I decided to switch from a regular form/subform to a linked subform in order to get more of the subform on screen - there are over 50 fields and controls on it. I have some fields disabled that should be enabled based on a command button click and vice versa with others. When I open the linked...

The problem was some extraneous code. I had deleted a command button without deleting the code for it. Everything now works.

When I click OK the halt window comes up. I've been playing around with this. It must be due to some underlying code (there is quite a lot on this form). When I create a blank form and add the macro, the macro works fine. I will see if I can find the code. I have the close buttons enabled so...

I am trying to close the linked subform from a main form using a macro. The macro simply closes the two forms. I am getting the error message you see in the attached jpeg. What does this error mean? And if I can't close the linked form this way would DoCmd do it? What would be the syntax?

Re: Cascading Combo Boxes Redux Sorry to bug you guys about this again, but I am really getting frustrated with this. I have gone over the examples that Bob did for me. I thought I understood them. I know I got this to work before but I can't get it working again. The form frmTrxns is based...

Although I am not a programmer/developer IT type, I can think of two items I'd like to see. One - the ability to undo deletes of objects like Forms etc. We can undo delete in almost every other aspect, why not with objects? Two - the ability to group objects together. For example a query...

Who needs good luck with you guys. This works like a charm.

Yes. That was the first thing I tried. There is a subform at the bottom of the form that seems to have taken control - at least it seems to have the focus.

This is a minor nuisance, but can it be fixed? Whenever I open a relatively long form (ie long enough that it extends beyond the viewing limit of the screen), the form always opens at the bottom part. This happens wether the form is opened from a macro and maximized or from the db window...