Another 'Command or action 'Find' isn't available now.' problem

[memilanuk]

Hello,

I've been fighting this one for a while now, and its about to drive me to drinkin'. Searched on another forum, didn't find much. Only suggestion there so far was to reinstall Access 2007! Searched here and found a number of threads with similar symptoms, but they each apparently had different solutions, which doesn't help me much. Any ideas or suggestion would be very welcome!

I had a fairly simple but functional database working. There were a couple pop-up forms activated from a master form for adding/editing or deleting individual records. These pop-up forms had several buttons on them, including a 'Find Record' button that did 'RunCommand' -> 'Find' on the field the cursor was currently in. Simple, and worked.

Then I decided to split the database into front and back ends. My first time at that and I was 'improving' some of the forms and reports at the same time. Got everything working on *my* computer finally and stuck the files on a usb drive to take over to the users house (we both work as part of a non-profit club). Later he called me back, as apparently the 'Find Record' buttons weren't working. When clicked, they just pop up a error message saying 'The command or action 'Find' isn't available now.'

I fought this for a while, and was really perplexed because all the other buttons *did* work, and it wasn't like 'Find' is trying to modify anything. Both computers are running Office 2007, mine running Vista (believe his is as well but not 100% sure). I went to work on it again this week after leaving it alone for a while... and now it won't work on *my* computer either. Everything else still works as originally.

The really weird part is that I have a split-table form that I have added several buttons to in the mean time... including what seems to be an identical 'Find Record' button... and it works fine. Just those two buttons on the two pop-up forms do not. I've tried deleting the buttons and recreating them, yet nothing seems to work. I've also tried creating them as macros and having the buttons use RunMacro, but that errors out as well. Again, just on these two forms.

Help!

Monte

 

[boblarson]

Find the code which opens the recordset and change it to have it use dbOpenDynaset

which is necessary on linked Access tables.

 

[memilanuk]

Ummm... guess I should point out that I'm still fairly green at this stuff

...so a) where would I 'find the code which opens the recordset' when I didn't write any code; everything was done with the button wizard. Not really sure where to look.

...and b) guess I'm not following why it matters on a pop-up form but seems to not matter on a split-table form which is literally looking at the same table in the back-end?

Thanks,

Monte

 

[boblarson]

It is probably an Embedded Macro so you'll have to go look to see what it is doing and the arguments it has.

 

[missinglinq]

Is the errant copy you're working on, on your computer, the original copy that was working? Or is it a copy of that file that you've copied onto your flash drive and then re-copied back to your computer?

My first thought, on reading your original post, was that you might have a corrupted file on the second user's PC.

There have been many reports of databases becoming corrupt when transferred via flash drives. The explanation I've seen is that many flash-drives report a transfer as being complete when, in fact, they aren't quite complete, and pulling them even a split-second early can result in corruption.

 

[memilanuk]

Mmm... no the problem is (now) on both computers, and while the front-end was transferred via USB drive before, the most recent version (today) was transferred via a DropBox public link.

Still not really understanding why I would have problems with the buttons only on pop-up forms, and not on split-table forms if its some underlying code issue with the use of a split database - doesn't seem to make much sense.

 

[memilanuk]

Okay... still gnawing away at this one.

The latest is that the button works as it should when I open the form directly from the left-side Navigation Pane... but not when I open the same form from the master form (my 'switchboard').

I think I'm getting closer, but if anyone has any ideas (other than reinstalling Access on the 3-4 different computers I've tried this on and gotten the same results, half of which I don't have admin rights to reinstall software...) I'm all ears

 

[ChrisO]

What default mode is the Form set to open in?

What code is being used by your switchboard to open the Form?

 

[memilanuk]

What default mode is the Form set to open in?

Pop-up: Yes
Modal: No
Default View: Single Form
Allow Form View: Yes

What code is being used by your switchboard to open the Form?

Embedded macro; using a simple OpenForm macro to open the named form.

 

[memilanuk]

Got it. I knew I just needed someone to prod me in the right direction

Turned out to be something I wouldn't have considered otherwise; the macro wizard for those two buttons on the 'master' form had window mode of 'dialog' selected, instead of 'normal'. Seems like 'Find' was about the only thing I had that wouldn't work in that mode, but changing them both back to 'normal' and leaving them as pop-ups appears to be working... on this machine at least. I'll have to test on the others as I get a chance.

Thanks,

Monte

 

[ChrisO]

A good outcome because you probably won’t be bitten again or, at the very least, you will know where the pain comes from.

 

[widemonk]

I appreciate this is an old post but similar problem, this solution of pop-up / normal window type didnt work for me...

On the Form_Load event, I run a series of checks to determine the day and even windows user login ID etc.

My form is essentially a list for user sessions. One record per user per day.

When my form loads, I want to systematically check to see if a session for today already exists for the user (if not, it reaches the end and creates a new record anyway).

So after determining the properly formatted date and user id, I have this, but I get error 2046 (command or action 'GoToRecord' isnt available now)....

      Do until DateNow = txtAuditDate.Value And AuditorNow = combAuditor.Value
        DoCmd.GoToRecord , , acNext
      Loop

Ive also checked its not erroring out at the last record because I've added a simple message box after the GoToRecord command to prompt that ts shifting from one record to the next, but the temporary message box never appears.

Any ideas ??

 

[ChrisO]

Best I can suggest is to not use it but use a FindFirst of the RecordsetClone instead.

Chris.

 

[ChrisO]

Best I can suggest is to not use it but use a FindFirst of the RecordsetClone instead.

Chris.

 

[spikepl]

GoToRecord is sensitive to where the focus is - or isn't - when you call it. Go with ChrisO's suggestion.

 

[CIS]

I have the solution
I have two weeks searching about this problem, and I solve it now.

1- Go to Form properties and make (Pop-up = yes)
2- Go to master Form and make the button that open Form to be opened in the normal form.

I am an access experience now