Search results

How are Open and Close time stored. For your example 11am - 2am means 11hrs to 26 (24+2) and 3pm = 15. If Close time< Open time then Close time = close time + 24. I would move to a 24 selection, keeping the above in mind.

I think that this is where your problem lies. If you are using more than 1 tbl, and tbls are joined, then you can only update where there is only 1 join fld which isn't Indexed, Duplicates Allowed - every other join fld has to be Indexed, No Duplicates. If there were 2 tbls and no Join fld you...

This one is a classic - there is an easy workaround. I got this from "Access97 Developers Handbook" Litwin, Getz et al. Dim db As Database, rst As Recordset, qdf As QueryDef, prm As Parameter Set db = CurrentDb Set qdf = db.QueryDefs("qrySomethingWithParameters") For Each prm In...

How do you stop users from "orphaning" records on the many side tbl.

Sorry just realised you've got the answer.

Can you give us any idea as to what info you're saving in the spreadsheet. eg Is every Mon the same or can info change from week to week. Have a look @ some of the other questions posted to get an idea.

The main feature of my qrys is the parameters ([Enter Open Date] etc.). I tend to probably break the data down into too many qrys. But I have been caught out several times so I stick to my method, which I know will give me 100% accuracy. You may be well right in what you are doing. I don't...

"If RFQLinetbl is your junction table, then if you just add 2 fields, SupplierID and RFQID" I think speakers 86 might be right. Put SupplierID into the line tbl and you won't need RFQID in the Supplier tbl. RFQ tbl to Line tbl is a 1:many (RFQID)and Supplier tbl to Line tbl is a 1:many...

Primary key (PK)- an index set to No Duplicates ie each value in the PK fld is unique, as you get when you use Autonumber for the fld. Foreign key (FK) - an index set to Duplicates Allowed in another tbl which can be joined (relationship) to the PK tbl. Usually both PK and FK have the same...

Just a guess, but the db might be corrupted. I had a similar experience, from A2003 SP3 to A2007, (not the same error) - the db was corrupted, but when I loaded a 2nd vs of exactly the same db, it worked fine (once security issues were resolved).

Have dummied up a db and am posting it - I've changed PersonnelID to EmployeeID. The qry with "final" in the name is the one that gives you the info as required for SL etc.

My mistake - PID should be "Group By", not "First".

I would do this by setting up a Group qry built from the sub tbl and a Select qry from the main tbl. Group qry: I always use the QBE grid unless I'm writing a UNION qry. I would firstly build a Select qry and then a Group qry based on that. (Because you need a date filter, I've found...

What name have you given to the qry.

If I understand correctly from what you have described (1 RFQ can have many Lines and many Suppliers), you will need RFQID in the other 2 tbls as Number, Long, Duplicates Allowed. RFQID in the RFQtbl should be Autonumber, No Duplicates Allowed. This will allow you to set 1:many relationships...

Thanks, Statsman and Stopher, for your detailed discussions and explanations of system.mdw. I had a very similar experience at a site where someone had fiddled with Access and set up Security. The users there were asked for a login and pwd before they could use any db. It appears that...

A few thoughts on the above: Will there be more than 1 record in tblCompany. If so I would definitely put in CompanyID pk for tblCompany. tblMaintenanceEvent: Get rid of the space between Maintenance and Event. Does this relate to any of the other 4 tbls - it appears that it does. If so I...

Person_ID in the Person table should be Autonumber (Long, No Duplicates), a Primary Key (PK). Person_ID in the Visits table should be Number (Long, Duplicates Allowed), a Foreign Key (FK). This will give a 1:many join. It looks like you have the FK indexed as No Duplicates.

Use "dd/mmm/yyyy". dd/mm/yyyy can result in the American date format, believe it or not. eg 2/5/09 2 May can show as 5 Feb.

Here is something to consider. I assume that both tbls have ParentID - Long, PK in Parent and FK in Child. If no entry is made into the Child tbl then there will be no ParentID in there matching the ParentID in the Parent tbl. I would write some code in the module section of the main form...