Search results

One form, two subforms in a new db. The three work well together, except when it comes to a new record. When I want to input details of a new record, the main form and a subform work ok, but the third subform won't accept anything. Any guidance, please, gurus?

Thanks, SJ, thanks Pat. I've been changing a one-table db over to a relational db. The problem was caused by look-up tables. I wanted to put info from the old text field into the new lookup field. However, I have been advised that lookup tables are a very poor idea, and having been shown...

WorkID is a look-up field, so its Data Type is Number. In the same table, DailyGrind is a field with the Data Type of text. I would like to update WorkID with the jobs in DailyGrind. Surely there must be a way to do it, gurus?

Hi SJ "Enter parameter values" for both tblMain.PersonID tblEmployees.PersonID ...

Access says No. I don't know why. INSERT INTO tblEmployees (Roots) SELECT Roots FROM tblMain where tblMain.PersonID = tblEmployees.PersonID; Be grateful for guidance.

Oh ... do you mean something like UPDATE tableOne FROM tblLookUp WHERE thisID = LookUp.thisID? But dooes the lookup table have the individual records? It's (they are) the one of a one-to many link ... Sorry, Pat, new territory for me. I'll give it a try this afternoon (or as soon as I can get...

Hi ByteMyzer Thanks for your help. What I have then is UPDATE tblEmployees SET UnitID = CLng(Hostel); UnitID is a Long Integer being part of a look-up table. Hostel contains the data that could be updated straight into UnitID, except that the warning says type conversion failure. Hostel is...

I want to say update set field1 = field2 But field1's data type is Number and Field2 is Text. (Field1 is fed by a lookup table). Am I doomed to go through the 700 or so by hand, gurus, please?

Many thanks, GHudson. Looks really interesting. Have 'borrowed' it from the url - nearly 1000 views! - and will have a good study of it a little later. Cheers

Hi SJ - I didn't get a notification of yours, so I've just found it. Yes, sounds good. What I've discovered, and came back to tell Hayley_Baxter is to put Me.UpdateTime = Now DoEvents on the form's beforeupdate. It works really well. Now I see that's what you are suggesting. Course...

One step ahead of the law, it's said.

Many thanks, Hay, all noted. Of course, MileOPhile, just down the highway from you, has a stock of never-before-known ideas. Otherwise, I'll hope to borrow your method. Cheers.

Thanks, Hay, very much. Very interesting. Liked your history db. I might - if you'll forgive me - copy it. But, first, because my needs are so very small, isn't there a simpler way? In mysql, I can have a Now() field that records (automatically) each time a record is worked on. Isn't there...

Is there a popular way to show when records are updated, with something like a text box with Now(), please, Gurus? It needs to be automatically enacted. (A box that they complete themselves gets quickly forgotten.) Then if the Client refers to records changed on such and such a date, I can...

You must be right - but I don't know what it was. However, deleted and reinserted and Find obliges. Thanks very much, lagbolt.

Thanks, lagbolt. I tried that, I tried everything I could think of, including deleting the name and retyping it. Perhaps deleting the whole file and entering the data at the end of the db might be an answer. But it seemed to be the combination of 'sze' - I suspected - that had the better of...

A customer's name is SZEE. Seek him through the SName textbox with Find, and Access can't find him. (Same in the table.) Seek him with a wildcard Sz* and there he is. I've tried it on another machine - also with Access2k - and it's the same. Is it an Access quirk? Is there an answer? (The...

Gentlemen, many thanks. I think, I believe, the db is now relational. Well, the copy of it seems to be. I just have to correct my mistakes and apply the change to the actual db. On a forum, I was told that every form should come from a query, and I have followed this style. In this case, with...

Cheers, Neil, Cheers, Pat. This gives me something to worry over. Your remarks are valued. I hope to let you know the outcome .. soon. Gratefully.

Hi Neil The db isn't working out too smoothly. I don't doubt it's things I'm not doing right. Here is an abridged version of where I am up to. It's marvellous of you to take a look. Cheers, and thanks for interest.