Search results

A bigger issue, underlying mass shootings and many times unbeknownst to many of us is that ALL of the shooters in mass shootings were on antidepressants that list suicidal and homicidal tendencies as side effects on their labels. Are guns the problem, or is it the drugs these psychos are on?

So, none of the fields are strings. This error is only happening in report view. I'm beginning to think it is a result of Access 2010's new "calculated" datatype. But, I cannot be sure. I have this returning correct values in layout and print preview: =CCur(Nz([Rate]*[Acres...

I should be returning a number as opposed to a string, right?

So, I've updated the control source to this: =Nz(Nz([Rate],0)*Nz([Acres Sprayed],0)*Nz([Cost/Unit],0)/(Nz(Len([Combo50].[Text]),0)-Nz(Len(Nz(Replace([Combo50].[Text],",",""),0)),0)+1),0) I know - overboard with the Nz(), but this still returns the #Type! error. Control format is set to...

I have this as the control source for a text box in the detail of a report: =[Rate]*[Acres Sprayed]*[Cost/Unit]/(Len([Combo50].[Text])-Len(Replace([Combo50].[Text],",",""))+1) In layout view, it shows the correct values as currency, in report view I get the #Type! error in that control. How...

That's creative. I like that. Thanks.

Guys, Can someone post code for counting commas/specific chars in a string? i.e. String = " A,B,C,D " CountCommas(String) would return 3.. ? My brain is beat for the day..

I've read it, an have corrected the issue already. Thanks. One was an imported table from the first database I ever made. The second was a lookup meant to be in a form. I understand the issues.

Aside from non-functioning buttons, does everything make sense with the version I uploaded? It should test out fine other than my lack of creating required fields, etc..

I think I put that lookup in accidentally - does it seem to have a purpose? Which one are you talking about? Should be at the form level, right?

I really don't want to get rid of the multi-valued fields. They're quite easy to use and maintain. I'll wait for someone with A2007/10 if I have to. Not trying to be rude, but I can wait on this.

:-/ I'm utilizing 2007-10 functionality. Sorry.

Hey guys, I'm attaching a copy my db for your review. If you can, please check out the structure of things, and suggest any changes. I'd greatly appreciate this. The main form I'm looking for critique on at this time is frmScoutingRecords. Let me know how I'm doing, if you'd be so kind...

Also, how do you keep the next (New) record from showing up in a continuous form until you want it - e.g. on a button click to a new record?

Is there any way to smoothly scroll a continuous form as opposed to scrolling by a whole record at a time?

I've got some semblance of a working form prepared, just working on some little details before I'd be comfortable with posting a snip of it -- is it possible to change the background color of a single record in a continuous form? I.e. highlight the record that the current requery of the pests...

Here are updated relationships: Here is the index for tblFieldRecJoin: Do I need to index the pest records in tblFieldRecInfo? If so is this how? (Although I understand its purpose, I'm new to the idea/implementation of indexing.) : Does this all look right aside from spaces and special...

I'll reorganize as suggested tomorrow and post the updated relationships and details to make sure I've got this right. You definitely understand what I'm trying to do, and I like you're approach a lot better than mine (obviously)!! Thanks a lot! I'll let you know how it goes.

This whole design works - functionally and hierarchically. The only thing I don't like about it is that the subform and the subform within that subform cannot be viewed as continuous forms, so the data entry person(s) would not be able to see all of their entries at once to double check their...

These are my relationships: One note per field in the same table. I think your missing something -- clicking the bottom right "+" button on the dark blue area duplicates everything in the dark blue area (i.e. a new record in tblFieldRecJoin and therefore a new list of pests as a new set of...