Datasheet View

[pwicr]

I have a number of questions regarding datasheet view:

1: is it possible to have a customized view for each person? (Long story: before me, the creator of the database allowed everyone to access the tables. I now have locked everyone OUT of the tables, creating a nice handy button on the form to go to the datasheet view of the form as this is the preferred view for a couple of people. not everyone wants to see ALL of the field that are in the form in their data sheet view so it would be nice to have a view for each person...ie: Sally's View, John's View...etc.)

2: Once in data sheet view I would like them to be able to just click one button to get back to Form View...I'm struggling with getting a "Custom" ribbon created.

Thanks,

 

[MikeFar]

As regards to different users, why not split the database any make different front ends depending on their personal preference?
Regarding the second problem, I would create 2 forms with identical combos, text boxes etc but with a different view. Than just make a macro to close one and open the other!

 

[missinglinq]

No need to do all that for Question # 2!

On a Single View Form you can use a Command Button to switch Views, but because Datasheet Views don't allow Command Buttons, I use the Double-Click event of a Textbox to trigger the code in going from Datasheet to Form View:

Form View to Datasheet View

Private Sub SwitchToDatasheetView_Click()
If Me.CurrentView = 1 Then
  DoCmd.RunCommand acCmdDatasheetView
Else
  DoCmd.RunCommand acCmdFormView
End If
End Sub

Datasheet to Form View

Private Sub AnyTextbox_DblClick(Cancel As Integer)
If Me.CurrentView = 2 Then
  DoCmd.RunCommand acCmdFormView
Else
  DoCmd.RunCommand acCmdDatasheet
End If
End Sub

Linq ;0)>

 

[Simon_MT]

Removing users from Tables is going in the right direction. But having to pander to individual preferences is rather odd and could be a weight around your neck. You need to take command of this project and try and standardise the input - Forms are the better for input control.

Simon

 

[missinglinq]

I have to agree with Simon on this! I've seen apps with two variations of a Form, where one was for administrative types and one for the 'troops,' with the administrative one showing things the 'troops' didn't have to/shouldn't have access to, but catering to an infinite number of preferences is almost sure to become mill stone around your neck, especially if something changes requiring the addition of new Fields.

This type of app simply has to be split into front end/back end, for a number of reasons. Not doing so will, sooner or later, lead to corruption and probably to timing issues. As to the issue of each user having need to see different Fields/Columns in Datatsheet View, they can simply

• Select the Column they don't want to see
• Right-Click
• Click on Hide Column
• When Closing the Form, answer Yes to the Save Changes? Prompt

The next time they open the Form in Datasheet View those Column(s) will not be seen.

Linq ;0)>