Search results

For the list of years: SELECT Year(Datefield) FROM Table GROUP BY Year(Datefield) For the months SELECT Month(Datefield), Format(Datefield, "mmmm") FROM Table WHERE Year(Datefield) = Forms!Form1!Combobox1.Value GROUP BY Month(Datefield), Format(Datefield, "mmmm") ORDER BY Month(Datefield)...

? Relative or not

Tony Ferrino. However,

territory in the

It means exactly what it says. Without a mail profile to use SendObject hasn't got an email provider to send from. Either create a mail profile or use a different method such as CDO.

Thank you all for your thanks. I've made a start on Chapter 2... watch this space for the next thrilling installment ;)

Yes, it's in the listbox properties on the data tab. It's not the default rowsource type and I don't think it will let you change it to Value List if the rowsource is a table or query. To remove items from a Table/Query type listbox change the rowsource to a filtered version.

oops, I mean err, yes, I knew that, I mean, err, I meant that :o I stand by the dimwit remark about the person making this decision (and coming from me that's saying a lot - it's a good job I don't work in accounts).

Two things: In the query put a Criteria on the Option field of No Change the code to Me.Parent.sfm4802.Form.Requery

Quite a nice demo but for a few issues: EmpName should be a No Duplicates index The comment in the code: 'If User Enters incorrect password 3 times database will shutdown is incorrect. It will shut down after the fourth attempt even if that attempt is the correct password (after showing the...

No, that is the downside to hiding the application window. I can't quite remember what I found when I looked at this but I came to the conclusion to do all reports in Word or Excel. Maybe others know of a way round it. Perhaps you could export them to pdf and open the pdf.

That is indeed true but it's very easy for someone who is expert in designing and coding forms to say and not so easy for the less experienced to achieve. That is why I think, at least at first, just concentrate on consolidating the tables into one or two tables (plus the Projects table) and...

Yep, you definitely do not want a separate table for each discipline. One table with a field showing to which discipline the record relates. You can then emulate those 23 tables just as queries of this table filtered for each discipline. Whether Project Curve needs to be a separate table is...

Indeed, Spike is right: I was being overly polite. It sounds like a terrible structure and you're starting to reap the (what's the opposite of rewards?) of it. In all probability all you need is one table other than Project that would store all the manhours for all the disciplines. Et voila...

OK, working backwards: Yes you would change it to For i = 1 to 231 (or more, the Case Else will just exit the loop when it gets to a number you haven't assigned a table to) Using Excel to build repetative code like this is quite a good method. However, it's probably indicative of something bad...

You could put the code in the after update events of both numeric controls (?). You would want the combobox to be set to Value List and don't Allow Value List Edits. Then set it's RowSource something like this (in sfrm1's module): Private Sub num1_AfterUpdate() UpdateComboList End Sub...

Something like: Sub ProjtoAll() Dim dbs As DAO.Database Dim tdf1 As DAO.TableDef Dim tdf2 As DAO.TableDef Dim Rel As DAO.Relation Dim i As Long Set dbs = CurrentDb With dbs For i = 1 To 100 Select Case i Case 1...

And lastly don't .Close dbs, at least not within your loop and there's no need to at all.

And are you going to have one sub for each relationship? (Sub ProjtoBArchitectMH()) A: That's hardly easier than drawing the relationships by hand. B: Much better to reuse the code and just loop through a list of table names and change Set tdf2 = .TableDefs!BArchitectMH each loop

I think that would be the name of the relationship CreateRelation("ID" that it's complaining about (the szRelationship field in the MSysRelationships table). I think every relationship needs to have a unique name. You'll need to change ID to something like: Set Rel =...