Search results

Max (Like First,Last, Min etc) refers to a fld in the SQL (qry). Max(MyDate) is the latest date, Min(MyNumber) is the lowest no. etc

Look @ the tbl in which the data is being inputted. It must have a fld with Indexed Yes No Duplicates - ie a Primary Key (PK). The data you are trying to input is attempting to enter records into the PK with those records having the same value as existing records in the PK. Make a backup and...

Series List subform When creating any objects in Access eg frms, qrys - don't put in any spaces. If (when) you have to use VBA code it causes hassles.

There is a book "Access97 Developer's Handbook" by Litwin, Getz, Gilbert which has a CD. This CD contains many sample db's one of which I'm sure has a db which shows all events firing and the order in which they fire. I have found this invaluable because quite often, events occur/don't occur...

It works because of the Parent Child link (SpeakerID). Create a Sessions form (frmSessionsSubform) and put in all the flds you want to see there - making sure that SpeakerID is there. Hide the ctrl with SpeakerID in it (Visible=False from ppties). Use the wizard on the Toolbox to drag this...

You can set SellingPrice = Null and in the query have something like: FC: Iif(IsNull(SellingPrice),Null,Pcntfoodcost = [ingredientcost]/[SellingPrice]*100) If there is no SellingPrice then leave blank, otherwise (the formula). Notice how I've removed all blank spaces and the % - good...

Yes - I just made them up and posted them in manually. You always add data to tbls via frms. In this case you need a main frm for the Speaker and a subform for the Sessions. They would be linked via speakerID and that would be automatically added to the Sessions tbl via the forms setup. As...

dbfixed. I had to delete the 1:1 relationship and redo after I made SpeakerID in sessions tbl Indexed Duplicates Allowed.

You have to put a SpeakerID in - it joins because the SpeakerID in the records of both tbls have to match. Make sure that you change SpeakerID in Sessions to Indexed Duplicates Allowed, otherwise if a Speaker has 2 sessions you'll only see one. If you are going to continue with Access, I'd...

Formula1 You have the same listed under General. I've answered yr questions there. WIS

Formula1 There is a very simple explanation - there are no SpeakerID's entered in the Session table. They are all blank. One speaker could have several sessions? If so, change SpeakerID Indexed to Duplicates Allowed. In general there are a few problems with the tbl's. 1 Instead of ID as a...

Very interesting - I am also running A2003 SP3 but I haven't bothered to run the "hotfix". I've identified about 5 bugs which affect me, but only 1 (the format in the tbl) gives me any problems. I have a workaround for that. To this stage I've experienced no problems as you've described.

What are the join flds. Pls list the fld name, data type and indexed type for both join flds and we may be able to help you. eg CustomerID, Long, No Duplicates.

This is a wild guess - run /decompile on the db. You seem to have very major corruption. Here is a site to explain and help on decompile: http://www.fmsinc.com/MicrosoftAccess/Performance/Decompile.asp

I don't think the "hotfix" will solve yr problem - I put this in to alert newbies and others of the A2003 SP3 problem and solution. Do you have CompactOnClose set from Tools->Options->General or do you run Compact and Repair.

On the parent form: OnActive Event Me.Refresh

Go to Help -> About Microsoft Office Access. If you have SP3 there are bugs in it that can be fixed via a Microsoft patch called a "hotfix" - you can find it on the Ms site.

Yes you are right - the table that the make table qry produces is deleted as the make tbl qry runs.

I assume that each deed has a unique number - ie no two deeds can have the same number. You don't need an ID number, the deed number will be the ID. Set the deed number as Long, No Duplicates and make it a PK. (I would call it DeedID with the Caption Deed Number). The Owner(s), Ancester(s)...

If you create a make table qry and a delete qry to zero all records before the make table qry is run, then the whole process can be driven from a cmd button. I never let users near the database window as objects can be easily deleted, especially by inexperienced operators.