Project Managment

[Homegrownandy]

I have a database that will deal with all aspects of a project. That's great. But currently when I want to use it on other projects or make a new project, I have to make a new front end that is specifically for that project.

What I'm doing now (working progress/subject to change) is having the user select the project on the main menu. This information will then be kept on an invisible text box on the background form.

Then, Any main form that opens from the menu will use this information in the query and only open information relating to that project. That's the best way I can think of for doing this. Any suggestions appreciated.


So, assuming that solution is the one I go with (its the one I'm working on). I'm having a few problems. This is code associated to the change event of the combo box on the main menu.

Private Sub project_Combo_Change()
DoCmd.Requery "project_combo"
Forms![background form]![Project_ID].Requery ' <- error occurs on this line
 
End Sub

I cant get either of these lines to update what's on the background form, the error I'm getting is: 438 : object doesn't support this property or method

I've had a look online and I'm confused as to what's causing it to be honest.

[Homegrownandy]

Changed it to:

Forms!background_form!Project_ID.Requery

getting the same error. NOTE: I have changed the name of the background form to include the underscore.

Its a syntax problem from what I read, ill keep looking.

then I've tried this:

  Dim ctlCombo As Control
 
    ' Return Control object pointing to a combo box.
    Set ctlCombo = Forms!background_form!Project_ID
 
    ' Requery source of data for list box.
    ctlCombo.Requery

I get type mismatch with this one.

[NTC]

okay - so let's review:
1. make a new front end that is specifically for that project: ** that is a horror show to be avoided at all costs

2. having the user select the project on the main menu. This information will then be kept on an invisible text box on the background form. Then, Any main form that opens from the menu will use this information in the query and only open information relating to that project.
** yes - this is the correct approach and is often used whenever one needs users to log in and to only show their information. This of course is all premised on that selected value being included in a field of every relevant table so that it can be filtered by a query

first - make your life simpler by putting that (hidden) value directly in a main form and not a sub form
second - give yourself a Start screen that opens initially and serves no other purpose than selecting the Project plus to hold buttons to the next screens/reports that people will go to - - this eliminates the requery requirements altogether
third - all object record set queries then have a criteria which calls to the (hidden) field held in the Start screen
forth - if a single user is going to change between projects - make that occur only on the Start screen - and rather than requery open forms/reports - force close them....this will in turn force the user the press the button on the Start screen and thereby refresh the data...

this approach is much less complicated and far more uniform and robust

[Homegrownandy]

The database was only used and built for one project, and its amended/updated on a priority need for the business. I agree it needs to be avoided. I have some questions, and I probably wont be looking to implement this until Monday now.


I agree with what you're saying I'm just struggling to visualise it. I may be making this more difficult than it needs to be so ill have a go Monday then update.

Thanks for the advice.

[NTC]

Fundamentally you need to insert a new Start screen that is the Project Selector - - and then take away any project selection from all the other screens, and rework their record source queries so they rely on the Start screen for the correct project criteria.

[Homegrownandy]

I understand that, but doing it that way requires the start screen to always be available?

Not a problem im just asking.

Theres not like a temporary memory after selection, It will always refer to that location. (I didn't get the chance to try this out, but thanks for your input)

[NTC]

I recommend the Start screen approach. With tabbed screens it just ends up sitting on the left and is easy for user to return to in order to select a different project. It makes it very clear to all as to which project is being worked on....But yes you can use a hidden form/screen to hold the value or do a DLookUp to call it from a table - or write it as a global variable to a module.

[Homegrownandy]

Thanks, I'll be able to work something out with your suggestions. Now all I need is time! haha