Results 1 to 5 of 5
  1. #1
    Join Date
    Mar 2009
    Location
    Gatineau, Quebec Canada
    Posts
    147
    Provided Answers: 1

    Unanswered: System adding {exp1:} to query fields

    Greetings again,

    I am building a database for a food bank located in Gatineau, Quebec.. We seem to be running into an intermittent problem with queries. From time to time, a query will add {exp1:} to the name of a field, in effect renaming the field and then the linked reports generate error messages (about the now missing field!). May have something to do with our doing the database on the extreme cheap: I have Access 2010 at home and upgrade the master on it. I then bring the master to their facilities, which uses Access 2007, then link the front end to the back end tables on the $200 WD MyCloud server. There are five connected workstations. The server, BTW, works surprising well. I know one should reinstall the front end on a blank database, but not doing so has not seemed to create problems AND reinstalling on a blank database has its own set of problems (with References, etc).

    Anyone have any ideas, or will I need to test every report every time before and after I reinstall (i.e. compile the front end)..

    Second problem, a macro one. I am at the moment a one man volunteer for the food bank's MS Access databases (donations, clients and volunteers), with no support. I am retired, and hope to find others locally interested in Access programming. No success. If I get run over by a bus (or keel over from a heart attack), months of data will be lost. Oddly enough, this food bank had operational Access databases before, but lost them when the sole individual involved left. Any ideas on how to develop a volunteer team locally (or otherwise)?

    Regards



    J. Smith
    Gatineau, Quebec Canada

  2. #2
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,424
    Provided Answers: 8
    exp1 mean you are doing somthing and the Query is just naming it for you


    if you went [qty]*[price]

    the SQL will put exp1:[qty]*[price] which is the name of the feild

    you can just

    Total_Price:[qty]*[price]

    remember DON'T use spaces in it Query will not be happy with you
    Last edited by myle; 09-28-16 at 21:47. Reason: spelling
    hope this help

    See clear as mud


    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB based on my own environment: vb6 sp5
    ASP based on my own environment: 5.6
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    MYLE
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.

  3. #3
    Join Date
    Mar 2009
    Location
    Gatineau, Quebec Canada
    Posts
    147
    Provided Answers: 1
    Thanks for the reply, and I often do calculated fields. This is a case where Access is adding a name {exp1:} on its own accord to the actual field names from a record. Recent case: it added {exp1:} to a field called "menage" (households) -- not a calculated field. One can change the name of a pure field with {xxxx:}; Access however seems to be doing this on its own.

    It crapped out, in one case, with this SQL:

    "Select distribution.menage as exp1:, max(distribution.ID) as MaxofID from distribution group by distribution.Menage."

    MS Access itself provided "MaxodID" as a calculated field name. When reloading to a blank database, however, Access chose to add "as exp1:"

    Thanks again for the response.

  4. #4
    Join Date
    May 2016
    Posts
    89
    Provided Answers: 4
    Hi

    In wizard tool = Total_Price:[qty]*[price]
    If you select SQL in Request Tool, you can see the SQL script => [qty]*[price] AS Total_Price

  5. #5
    Join Date
    Feb 2004
    Location
    New Zealand
    Posts
    1,424
    Provided Answers: 8
    Thank Informer I for got about that in the SQL
    hope this help

    See clear as mud


    StePhan McKillen
    the aim is store once, not store multiple times
    Remember... Optimize 'til you die!
    Progaming environment:
    Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
    VB based on my own environment: vb6 sp5
    ASP based on my own environment: 5.6
    VB-NET based on my own environment started 2007
    SQL-2005 based on my own environment started 2008
    MYLE
    YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •