Search results

Can anyone tell me where the "reputation" thingie that appears near the upper-right corner of these posts comes from? It appears as one ore more green dots or one or more red dots. Mine recently went from green to red, and I'm wondering if it's something I should worry about... this forum is the...

OK, I may be getting closer to the source of the problem. Since the "lostpersetup" field seems key, I went back to look at the ByPN_1 query. I changed the lostpersetup field from to a "group by" instead. That makes the problem go away. I sometimes use "first" as a shortcut when I'm dealing...

So here's yet another wrinkle. This query is fine: It returns: But if I do nothing more than add the "lostpersetup" field a 2nd time (regardless of whether I then try to perform any calculations on it) I'm back to: Surely it's not a no-no to use the same field twice in one query????? I...

Pat, I tried totally rebuilding the db using the method you suggested. No change. Doug, thanks for your observation. I already know that I can make this problem go away, in this instance, by breaking the query down into multiple queries. What I need to figure out is exactly WHY this happened so...

Thanks for taking a look. In response to your points: I have attached a new version the database which addresses most of your points, but still has the problem query. 1. I had removed the lookups but it made no difference so I re-added them, as I find them very useful. However, I have...

Here's the database. I've named the offending query "BAD". I really appreciate any help you can offer!

It's been suggested that I report this problem to microsoft. How do I do that?

I have now split my original query, which was very complex, into 8 separate, sequential queries -- by sequential I mean that query #8 runs from the results of #7, #7 from #6, etc. In my original query I had many calculated fields where calculated field B depended on the results of calculated...

Tried it, no change. BTW, I have simplified my offending query down to: "lostpersetup" should show an integer value but instead is returning the results from a nearby text field in BYPN_1. I can control what "lostpersetup" returns by changing the order of the fields in ByPn_1.

No, I am using Access 2002. I have to say, this really scares me. If the "wrong" field that Access happens to pick, happens to be an incompatible data type with the correct field (text vs. number, for example) then I'll notice the error. But if the data types are compatible, I may not notice it...

OK, I have removed all traces of any lookup fields from the tables involved with this query. No change. Furthermore, I can change what shows up as the erroneous data in the LostPerSetup field by changing the order of the fields in ByPN_1. Seems that whatever I put as the 3rd field in ByPN_1...

Well, yes, I have several. ByPN_1 is, itself, a query based on 5 tables. 3 of them have one field each with a combo-box lookup defined. So what is your question driving at? Are lookup fields a known problem?

This is at least the 3rd time I've come across something that is, to me, an extremely serious bug in Access. Anyone else seen this, and anything I can do to avoid it?? In a query, I ask for the values from Field A. The query returns the values from Field B, but still calls it Field A. This is...

Access 2007 runtime, still getting security warning Thanks, that certainly looks like it would help, but after manually editing the registry I'm still getting the security warning. (at least I didn't seem to break anything). My "trusted location" is on a network drive, not a local drive, so I...

I am not doing anything like "packaging my application for deployment". My applications are all used internal to my company, and I just 1. Install Access runtime 2. Copy the FE onto the PC. This has worked fine for me for many years... up until Access 2007, with it's additional security...

How in the world do I add a trusted location with only the Runtime version of Access 2007 installed on the PC? I am in the process of distributing some new runtime-only applications; how do I stop the irritating "potential security risk" warning from coming up everytime the user logs in??? I...

Hi, I have a form named "setup", that consists of nothing but a bunch of interdependent listboxes. The rowsource for listbox 4 depends on selection in Listbox3, Listbox 3 depends on selection in Listbox 2, etc. The form works just fine, except that when I close it I often (but not always) get...

I changed to using a subroutine rather than calling the CurrentEvent directly. Still getting the same error message: err.description = {blank} and err.num=0 Any other ideas?

YOu can use the SourceTableName property of the TableDef object. If Len(SourceTableName)>0 then it's a linked table.

Thanks, Will try using a subroutine rather than using form_current, and see how it goes.