Recent content by WIS

Have you tried this: This solves the "Too few parameters - expected nn". Courtesy of Litwin, Getz et al Dim db As Database, rst As Recordset, qdf As QueryDef, prm As Parameter Set db = CurrentDb Set qdf = db.QueryDefs("qrySomethingWithParameter") For Each prm In qdf.Parameters...

If you try to enforce RI after the tbls have been inputting data for a while, it usually comes down to "orphaned" records on the "many" side. What was the actual message you got trying to enforce RI.

With a split db, put the be on the server and the fe on the client PC's. Hint: Put the fe on the server, link to the be and then copy the fe to all client PC's. If you need to change the fe, have a vs on a PC which can be updated, then copy that to all PC's as before. I never develop the fe...

In versions of Access prior to A2003, it is possible to disable the "AllowByPassKey" ppty even when it set to False.

A subform is placed on a main form, but it needs to be placed in a SubForm/SubReport Control. Get the main form in design mode, go to the Toolbox on the Toolbar and select SubForm/SubReport. This puts a control on the main form with a label "Childnn" and a "text box" called Unbound. This is...

Problem: You have Sub testdate(t1 As Date), but then you have t1 = Format(t1, "mm/dd/yy"). t1 has changed from a date to a string - that's why you need the # around it.

In the Format ppty of the fld in the tbl put ">" (without the ""). Also put it in the appropriate ctrl on the frm. Note: If you have A2003 SP3 this will NOT work due to a "bug" - you have to apply the "hotfix" first.

Some questions: What vs of Access is it? Does it have a pwd as you try to open it or is it using Access security (eg User/Groups with a .mdw file).

You must have "AllowZeroLengthString" ppty of the fld in the tbl set to "No" - this will disallow the "". Set it to "Yes" if you want to put "" in the ctrl (hence fld).

1. With relationship set and no RI etc you can delete from Carrier but it will leave the few appts as "orphaned" records. 2. With RI set you have to delete the appts before it will let you delete the Carrier. 3. With "Cascade Deletes" set, if you delete the Carrier it also deletes any assoc...

Relationships between tbls (with RI set) prevent things such as "orphaned" records - you delete a record in the main (PK) tbl and leave a no of associated records in the secondary (FK) tbl. With a couple of tbls this may not be a big issue, but with a 100 or more tbls things can get out of...

Access has "Replication" for doing this sort of thing - I've never used it but perhaps some others have.

I've just put this on the General of this forum for a problem which looks a bit similar: Courtesy of Litwin, Getz et al Dim db As Database, rst As Recordset, qdf As QueryDef, prm As Parameter Set db = CurrentDb Set qdf = db.QueryDefs("qrySomethingWithDateFilter") For Each prm In...

In the Criteria cell put: Between forms!myformname!mycontrolname1 And forms!myformname!mycontrolname2 where mycontrolname1 and 2 are the 2 dates. (Note: Use the name of the ctrl, not the fld name)

Is this the only "corrupted" record in the tbl. Is there a PK (Autonumber) eg xxID. If so run a make tbl qryup to xxID 1 less than the "corrupt" xxID. Add a dummy record at the end of this tbl (to keep the xxID Autonumber in synch). Run a make tbl qry from 1 more than the "corrupt" xxID...