Cannot Open Form in Datasheet View from Command Button

[JoeM]

I am using Access 2007 and trying to open a Form in Datasheet view via a command button. I have the following code to open it:

Private Sub cmdDefaultElects_Click()
    DoCmd.OpenForm "frm-Default_Election_Amounts", acFormDS
End Sub

However, when I click the button, it opens in the default form view (single record at a time) instead of Datasheet view. If I open the Form directly from the Objects menu, it correctly opens in Datasheet view.

I have even gone into the Properties of the Form and changed the following:
Default View: Datasheet
Allow Form View: No
Allow DataSheet View: Yes

But it made no difference when trying to open it from my Command Button.

Any ideas why this is happening, and how I can get my Form to open in Datasheet View when opening from a Command Button?

[June7]

Cannot replicate the issue. If you want to provide db for analysis, follow instructions at bottom of my post.

[Missinglinq]

I can't, either, and Properties set in errant Form's Properties Pane has nothing to do with how it opens, using a Command Button, that's why you have to use the Form View Parameter of acFormDS.

When things that patently should work are found to not work, you simply have to think about corruption! First thing, I'd do, after saying a prayer to the Access Gods (or maybe the Access Gnomes!) would be to delete your current Command Button and re-create it. It's simple enough to do, and would rule out whether or not it is the Command Button Control that is corrupt. CB's cand and do get corrupted, on a regular basis, during development.

Linq ;0)>

[JoeM]

delete your current Command Button and re-create it

Well, hot dog! That did it! Not sure how a brand new Command Button I just created yesterday got corrupted, but re-creating it did indeed fix the probem. Thanks for the suggestion!

I am glad that worked, because it would have taken a lot of data scrubbing and deleting to post the database up. Most of the data comes from linked SQL tables, and there is a lot of confidential information in it.

[Missinglinq]

Glad we could help!

Being in forced retirement, I spend 8-10 hours a day, most days, trolling and contributing to four or five Access forums, and see this problem posted at least once every single day! Actually saw it three times yesterday!

As I said, it appears to almost always happen during development, never after the app is deployed. No idea why that is!

Good luck with your project!

Linq ;0)>

[JoeM]

Its funny, I create stuff likes this all the time (using Command Buttons and VBA code), and hardly ever have issues with it, so I assumed that I was missing something. I have had Databases get corrupted, but rarely Command Buttons! But then again, we all know how "flaky" Access can be at times. I should have thought to try to rebuild it...

Thanks for the reminder!

[Missinglinq]

This type of thing comes under what I call Strange, Odd and Curious Behavior, and S/O/C/B, when something that patently should work but doesn't work, usually translates into corruption, in one form or another. Don't know why Access is so susceptible to corruption, except that it is such a complex app.

Linq ;0)>

[JoeM]

This type of thing comes under what I call Strange, Odd and Curious Behavior, and S/O/C/B

Yep, there's not shortage of those things in Access!

Can't tell you all the fun "differences" we found between Access and SQL when we moved a database from an Access back-end to a SQL back-end!

[STONEE]

If you are using access 2010 or later, do not use the properties panel, it will only revert to form view.
Go to the embedded macro viewer and when you open the form, go to the view dropdown and select dataset.