Search results

Edit: sorry comment removed. A bit too facetious. (I suggested the magic (code) could do with improving.)

Couldn't Access let datasheet view records each have their own individual focus simultaneously? Or is that going to be a massive hardware resource hog?

Fair play, I've checked and you did indeed. I even said I'd look at it. I got a little side-tracked by taking offence at something, and forget to go back and reconnect with the substance. Well, I was up really late at the time, but I owe you an apology.

Did you say that (pop-up form suggestion)? I'm sorry I didn't pursue that. I'll go back and review our other conversation to see where you mentioned it.

Look with an ordinary form, even if it has cascade lookup elements, every record is displayed correctly as you move from one record to the next (I think, anyway, I haven't done a thorough check, but I'd darn well hope so). But with datasheet view, with a cascade lookup the master combo box...

I think what Glaxiom is saying is that Datasheet view is not compatible with cascade combo boxes/lookups if I also want the Datasheet to display itself correctly at all times? I hope not. But popup forms.... I will look at them next. I do hope they aren't another aspect of Access which seems...

Oh for goodness sake! I'm rapidly losing patience with Access. This is RUBBISH. Surely that does not have to be that way?

JANR, thank you for that. I believe it is an attempt to tackle the problem I'm facing. However, I have to admit I don't like it. I want a clean 'active spreadsheet' kind of look that datasheet view gives me. With row after row of records with many fields, all those drop down arrows in the...

Bump. Any chance of answer on this? I've now tried violating normalisation by creating a Building field in my main table (not necessary data-wise because "building" is implied by the "room" field that's already there). This results in the Building FORM field displaying correctly in datasheet...

I would like to use datasheet view for what is probably the most important form in my database. I like/need its unfussy ability to display large amounts of data at once, such that moving the eye from one record to another and back is very easy. I also really need cascade lookups. But my...

Yes, and you'll notice I didn't raise any objection to your post #18, where you said perhaps. It was you saying: "you are using my database in a manner it was never intended to be used" that I was reacting to. I wasn't using it in any such manner, only investigating it to see if would help...

That's a bit rich! I indicated that I want to use a datasheet view form in posts 14 and 15 of this thread, and you then provided your example in post 18 to see if it helped me to create a form that did what I was after (thank you for providing the example). I was only looking at the example to...

I've probably made a mistake. I've gone and titled this thread with the word normalisation. I did want to touch on that, but I suppose its really about how I can create my form to do what I want, and whether it will be necessary to move away from ideal database design to achieve that behaviour...

I was kind of hoping for an NF1 or NF2 answer on my first point. On the other point, I may need to repeat myself, please read carefully: I'm gratefull for any answers, I just feel the two answers I've got so far didn't really engage with the specifics of what I'd said in this particular...

As a beginner I am not as familiar as most here with normalisation. Consider a Buildings table lending a foreign key to a Rooms table that in turn lends a room foreign key to an Equipment table. Building>Room>Equipment. I imagine that re-recording the 'building' characteristic in a seperate...

...of course having a form in datasheet view does not work well with unbound form fields unfortunately.

No. When I was talking about columns I meant form fields viewed in datasheet view. I have a particular interest in form datasheet view, partly because when I started out with Access I didn't know what I was doing and DID use tables directly and got used to it, but partly because viewing one...

I know it was a few posts back, but I did say.

I can't duplicate it either. Perhaps I failed to click on 'enable macros' when I first opened the database. Just a guess. Now, though, I still see only one state displayed in the state column of frmAddress. If I click on a suburb that is in South Australia, then South Australia fills all of...

JANR, thank you. I did actually manage to work that bit out. It was the VB "requery" code for the after update event that I was missing. I managed to find that too (eventually). As a beginner I was not familiar with the VB editor or these after update techniques.