User Profile

Collapse

Profile Sidebar

Collapse
inglesp
inglesp
Last Activity: Jul 29 '08, 12:33 AM
Joined: Jan 17 '08
Location:
  •  
  • Time
  • Show
  • Source
Clear All
new posts

  • inglesp
    replied to date format apparently changing mid-program
    Thank you so much - that was really helpful!
    See more | Go to post

    Leave a comment:


  • inglesp
    started a topic date format apparently changing mid-program

    date format apparently changing mid-program

    Hi everyone

    I've come across some perculiar behaviour in a little database app I'm making with Access.

    I have a form for users to create a filter for data that goes into a cross-tab query. One of the filters is by date - users can choose a start month and an end month. From this, I construct a string - something like "between #1/7/2008# and #31/7/2008#" - which I then use as a where condition in the sql statement...
    See more | Go to post
    Last edited by inglesp; Jul 28 '08, 10:45 PM. Reason: typo

  • inglesp
    replied to Naming reports created programatically
    puppydogbuddy

    That's really helpful, thank you!
    See more | Go to post

    Leave a comment:


  • inglesp
    started a topic Naming reports created programatically

    Naming reports created programatically

    Hi all

    I'm creating a number of reports programatically , and I'd like to be able to name them sensibly. However, when I try something like
    Code:
     rptNew.Name = "something sensible"
    I just get told that "this property is read-only and can't be set".

    Am I trying to do something you can't do? Or am I just doing it wrong?

    Thanks in advance

    Peter.
    See more | Go to post

  • inglesp
    replied to Problem editing data in queries
    Thank you for your ideas...

    @dbpros - yes, all the tables have primary keys.

    @DLN - none of the reasons your book suggests for not being able to update records match in my case. Unique values is set to no; I don't know what self joins are, but if they're what they sound like, I haven't used them (and you can check the SQL above); there are no aggregate functions in the SQL; each table has a primary key defined.
    ...
    See more | Go to post

    Leave a comment:


  • inglesp
    started a topic Problem editing data in queries

    Problem editing data in queries

    I was wondering if anybody could help me with the following... which is related I think to my question here
    http://www.thescripts.com/forum/thread780631.html

    I have two queries which are based on three tables - q1 is based on t1 and t3, q2 is based on q2 and q3. Each table has the fields {HID, yr, mo} and then some data fields. Each has {HID, yr, mo} as the primary key.

    The two queries are structurally identical,...
    See more | Go to post
    Last edited by missinglinq; Mar 11 '08, 06:29 PM. Reason: Add URL tags

  • inglesp
    started a topic Form not displaying when new record is added

    Form not displaying when new record is added

    Hi there

    I have the following problem, and I was hoping that somebody might be able to show me where I'm going wrong.

    I have a form - Form1, say - that takes its data from three tables: facs, which is a list of health facilities, and two tables which just contain data. I have a second form - Form2 - which lists the health facilities, and for each health facility there is a command button which opens up Form1 for the...
    See more | Go to post

  • How to refer to a control created by CreateReportControl?

    Does anybody know if it's possible to specify the name of a control created by CreateReportCon trol?

    I have
    Code:
    txtNew = CreateReportControl(...)
    and I can refer to the control as txtNew immediately after it's been created, but this is no use if I want to create several controls in one go and then refer to them later. I've tried
    Code:
    txtNew.name = "newname"
    but then if I try to set
    Code:
    newname.Value = 5
    I get error "Object Required"...
    See more | Go to post

  • Explanation for limit on table widths, and how to avoid wide tables...

    Hi there

    I've searched here - and elsewhere - for an explanation of why Access limits the number of fields in a table to 255. I would guess wide tables are unwieldy to query, and so on. I've also read that database experts would consider an overly wide table (more than 30 fields?) a sign of an unnormalized data set.

    I'm currently working on a database to for the results of what is, in effect, a large survey. There...
    See more | Go to post
No activity results to display
Show More
Working...