Search results

Pat: If you have a moment, would you expand on that? I can see either tblDefendants having TWO fields (lngChargeModifierID and lngChargeID) or one field that points to a value in a junction/look-up table which stores the possible combinations of the charges and modifiers. Are either of these...

Nope, still there. Click on the link I put in my post above. But first, u/l the condensed db so KevinM can continue giving you excellent help. --Replay Mac

On a side note, Wesley, if you're asking a question you know has already been answered (seeing as how you asked it yourself and all), you could search the archives, say using your own username, and turn up the answer you got last time. --Reminder Mac (OTOH, KevinM - excellent advice given on...

Well, you've already gone right past the limits of my concrete knowledge--I thought you were asking a very different question (about DEVELOPING an Access project as a team via the web). However, based on what you've said above, it sounds like Access + WAN = bottleneck, so I ask: Is it...

Providing a few more details would be helpful, but I don't see why not, if you're willing to invest the time to work out the logistics. --Optimistic Mac

Look around for info on bookmarks, as well as perhaps multi-select list boxes--there's all sorts of improvements to be made on that basic idea. --Progress Mac

And another thing... If a workshop is offered more than once, put the date into the junction table and make all three primary keys. Read this thread (which also links to another thread in which the great Pat Hartman has a sample you can d/l). --Archive Mac

Junction Tables Search MS Access Help and these forums for the phrase "Junction Table". Given: tblParticipants autoParticipantKey = autonum (PK) txtParticipantName = text (etc., etc.) tblWorkshops autoWorkshopKey = autonum (PK) dtmWorkshopDate = date txtWorkshopName = txt (etc., etc.)...

Something like this VERY quick-n-dirty example. I'm sure the gurus hereabouts have much more elegant solutions, but this will get you started on designing your own. You may also want to search the archives here, I'm sure somone has u/l'd a better way at some point. --Harried Mac

I haven't had a chance to try this yet, but what about a main form with up and down buttons and a subform listing the info you want to see in a continuous-form listing? Highlight a record on the subform, click a button, have the OnClick property adjust everyone's priority and refresh the...

Apologies CQ - Don't let my crankiness ward you off from these forums. They are an amazing resource and everyone here is generally more than happy to help out newbies. There has been a recent rash of students, however, that have basically been asking the folks here to do their assignments for...

Ok, that IS odd. I would try (just out of desparation) refreshing the records just before the snapshot is created. If that doesn't work (and this is REALLY kooky), set your macro to create the snapshot twice? --Stumped Mac

Not sure what I said that was "so mean", but... As to whether or not you have to start the tables all over again, that depends. Fields can be added to the existing design fairly easily. Add the autonum field to tblPublishers, refresh the records, then go back and set that as PK. Then un-set...

Snapshots are static, not dynamic, so it's not going to update with new data. Think of them as a "print to file" sort of thing. If you have the db always running, you could put an OnTimer event to create a new snapshot and save it over the old one. Otherwise, if you're an .asp guru you can...

That's true, but there are all sorts of other reasons not to use the name as PK. --Multipurpose Mac

You shouldn't be using the publisher's name as your foreign key. In both tables you should have a field that is typed autonumber that serves as your primary key, something like this: tblPublishers autoPublisherKey = autonumber (PK) txtPublisherName = text tblBooks autoBookKey = autonumber...

First, stop shouting. Second, search MS Access help on "security". --Quiet Mac

A question for you, polina. How long will this "history" of the publications go on? If you are going to have to add a new field to your table every month to store the number of pages for that month for that publication... you're going to have a very long record structure very quickly...

Thanks, Pat. This kind of answer is the main reason I love this forum. --Grateful Mac

If you set the Lookup property in your table design to open a combobox pointing at the table that contains the workers' names, it should carry through to queries (but not SQL stuff...) i.e.: tblWorkers: autoWorkerKey (PK autonumber) txtWorkerName (text) tblReceipts: autoReceiptKey (PK...