Recent content by stevehooley

  1. S

    The Department of Positive Out of Body Possibilities

    Hi everyone, I have been following this quite unique thread for a while (probably for too long in truth) and i would just like to comment on the following quote from Mike.G: The idea of sending that to the fire service had me in stitches. Bordering on comic genius...:D Cheers, Steve
  2. S

    Charts Criteria

    Could you apply another query that removes the blank dates, and then run the chart off that? I'm not too good with charts but I assume that if you have an axis that it time-based and you try and remove days from it, logically it will have problems.
  3. S

    specific normalisation question

    Hi Ken, Thanks for the prompt reply. Seeing those team_ids repeating in the columns just caused me to question it for a moment. I'll plow on...
  4. S

    specific normalisation question

    Hi everyone, I'm trying to get to grips with normalisation as it applies to a specific example database I'm working on (that I will ultimately be using to teach other people :eek: ). If anyone could help with the following issue I would be very grateful: I have a table of football (or soccer)...
  5. S

    Combo Box filter

    hi bunji, maybe try .Requery rather than .Refresh for the combo box
  6. S

    Uh oh... I have a problem

    Hi jetstrike, If you know how many people answered in total you can do the following: no. for question 1 (and 2, and 3, etc..) ----------------- total no of people If you then put this figure into a field in the report as a 'percentage' format it should show what you need. If you don't know...
  7. S

    Multiple users trying to access reports with append queries ::Please Help::

    Hi gold007eye, Firstly I would avoid appending to a table for the generation of a report if possible (rather use a query that filters from an existing table and can be accessed by many users). If the append method is the only way, have you considered having another, one record table that...
  8. S

    two sets of criteria select query prob

    criteria Hi Steallan, It looks to me like the criteria you entered is telling the query to take records that are like pendant and not like 6077 OR like pendant and not like 6074. That's why its giving all records like pendant. You may want to put: <> 6077 and <> 6074 for first field like...
  9. S

    What's your best/worst joke?

    really rubbish one Q: How do you turn a duck into a soul singer? A: Put it in the microwave until its bill withers. :rolleyes: :D
  10. S

    auto-number madness

    that could be it, thanks for your help. :)
  11. S

    auto-number madness

    Hi everyone, i hope all is well. In one of my databases, an auto-number field seems to have reset itself without manual intervention (e.g appending a long integer value). Does anyone have any suggestions for how this may have happened? :confused: :eek:
  12. S

    Inverted values on a form

    options box? if you add an option box to the form and link it to the field1 you can toggle between the true and false values. By their nature option boxes with two values will always show the inverse. although this would mean the field1 value would not be hidden :o
  13. S

    How to reference form field with AND or OR criteria

    i hope this helps is this ok? the pic shows the query builder screen in design view. this will give you a query showing all the records in the RESULTS_TABLE that match with any parts in the ENTER_PARTNOS table
  14. S

    How to reference form field with AND or OR criteria

    what about?.... What about creating a table (rather than a single field) where you can input the part numbers for the criteria? Then you can query this with the table you want the results from.
  15. S

    oracle linking problem

    Hi everyone, I'm linking to ORACLE tables in my Ver. 97 MSaccess db. I've used the Oracle ODBC driver to link them, and they have all worked apart from one. The one failure shows "#Deleted" in all the fields, although there are the correct number of records. Does anyone know why this may have...
Back
Top Bottom