Search results

You are in luck...I am a bowler! (598 series last night...2 pins UGH!) Anyway...here is probably what I would do - though this could be more than you are looking for haha. PK = Primary Key FK = Foreign Key tblBowler --------- BowlerID (PK) FirstName LastName PhoneNumber (Any other personal...

You could also use DateAdd function and add a negative 1 :)

See I don't even do a repair on the back end when this happens - I just replace the users front end and everything works. I run a program which does a repair/compact on all of my back end files daily which runs before anyone comes in for the day, so that also greatly reduces the chances of data...

The records are probably not actually deleted. I run into this from time to time with my front ends. People get records that say #Deleted for everything, but it's fine in the backend and for everyone else. Replacing the front end with a copy of the original fixes it right up. Repair/compact...

The problem with continuous forms is that you cannot specifically select a record to copy unless it is either: A - Already selected by a user B - Identified by using a uniqe ID Have you tried stepping through your code? I get an error on: DoCmd.RunCommand acCmdSaveRecord It says that...

Why can't you just print a report from Access?

I've used this code before and it works fine as long as they have a record selected to copy from. We'll have to see a sample form or something.

What line is it erroring on?

I run Vista Ultimate at home and it's nice. It loads things much quicker for me, etc. I don't know that I'd want to push it out into a business environment though - it just doesn't seem ready for that. The only thing I'm unhappy with is their networking implementation - it's clunky and...

Yeah I just asked the question to get the OP to recognize an issue with the design :)

Yup. But what if you have two people with the same name? How are you going to differentiate between them?

An Update query should do this with no trouble.

Vista runs great for me. Loads stuff quicker. I haven't bothered putting SP1 on though.

I agree. You will also usually get some technical support with a retail package should you need it - and if it's a popular package, there is usually good information on typical problems.

You will probably have to make a new security mdw - I don't know much about them as that's not the way I handle security. But as long as you yourself have access to the data (back end) and production (front end) files, then you should be fine. You just have to redesign something that will work...

I would use an option group with all the different options for queries. That way you can easily see which option is selected currently. After changing the recordsource, you may have to do a Me.Requery. Not sure though. I've never had a need to make a form do that.

If you tell it to. You need to have a condition put on the primary key. So if it's the Req#, then you just need to have the update query match the Req# from your temporary import table to the main table, then update the status field from the temporary import table. The query will only change...

Read up on using a front end/back end solution. In this way, the back end with the data should not get corrupted (do a daily compact/repair on it before anyone starts work). If the front end on the users computer gets corrupted, you simply replace it and that's all.

Well for one, you have the variable num. You set it's value to 1 and never change it throughout the whole program. You can just type 1 in instead of the variable num, but I suspect you've forgotten to increment it. That may not be your error but we'd need the actual error and such to help...

Why? You can have them using the same database file and just adding info in. No need to do that I don't think.