Search results

This might sound ridiculous but this is all I can think of. [PREFACE] I have a split database, Front end Local, Backend on a LAN. Half our group is on west US, the other on the East. The LAN is out west, so the database runs great out there, out east - not so much. I've tried getting an...

Yea the all is the rub, because of the future. I'm glad to hear you say junction table, because that's how I have it set up, but it obviously contains a lot of records, because of each separate year being a record. I guess I can write some code that updates it for the future? I dunno, I'd...

Gotcha, sorry to be so circumspect I'm just trying to think of an example that isn't the actual example haha. (I don't know why I didn't think of the below example in the first place) Lets think of it as a year. So say we have a list of documents. I have some data associated with the...

Ah, sorry for not being more clear. Ignore the field title. It's just a field that is normally a single integer, that could be a value between 1 and ~40. But it's possible it could be a range, or "All"

I'm trying to figure out how to design a table or tables to handle the described case.

This is similar to my other, just posted question (apologies), but a bit different and much simpler. Need to record the "Affected Cycle" you enter an integer like 1 to 50. But it is also common, to affect "All Cycles". How should this be handled? In addition: What if there is a range of...

I have a many-to-many table (I'll call it a Joiner table, is there a real name?) that has the fields: ID_Note, ID_Unit, ID_Calc, ID_Widget Type. ID_Note is the "main" field, I have a form that is bound to the ID_Notes and a subform where you choose your ID_Unit, ID_Calc and ID_Widget Type...

So your comment made me break down and eliminate my vba functions in favor of pure SQL queries. I hate doing that because it creates a bunch of queries instead of one neat functions, but I can't argue with the speed - it pretty much halved my opening time. On my original question, I'm...

I think this might be a "no duh" question but I have a field in a query: PorC: IIf([d_Notification]>LastRepDate([txt_Plant]) And [d_Notification]<=RunDate(),"Current","Prior") It returns whether the notification is "Current" or "Prior" based on some fun stuff. Other queries use this field...

I want to add "record numbers" in a query based on more than one field. Notice how the "Want" column resets ordering at a new person, and doesn't increment when Person & Field 2 are the same. I can do this with more than one query, but I was wondering if there was a more concise way (With...

I've attached a word document of what the report would look like... kind of. Each location can have multiple sites. The errors can affect multiple sites. The prior/current comes from when the error was found. Notice how the notes appear for both sites, but for one location on the last page...

I have a basic table: Vendor, Error Date, Error Title, Error Notes. I would like a report that: Groups on Vendor, Is filtered by date. The error titles for that vendor would appear on one page. Then the error notes would appear on a subsequent page for readability. (Notes are long memo...

Do you have a specific table in mind that needs normalized, or should I revamp the whole thing :confused:? I can see where it would seem "unnormalized" with the Major Member 1,2,3 etc. so that could be put to a separate table. Regardless of that though it still seems that I would need to...

I have a database and I constructed all the tables and was going about adding relationships to them. I tried to add those weird relationships where it puts the number after the table name (someone please tell me what that's called :)) Maybe I shouldn't add those sorts of tables in the...

So I'm maintaining a database that stores employee info. When an employee leaves there info no longer needs to show up in many of the forms/reports etc. However some reports and such refer back to the past when that employee was still there (the Employee ID is still referenced) Up till now...