Replies

OK. That works. I will go with the multiple front-end solution for now.

I worry about the cashier creating another user and doing bad stuff under a
false cashier’s name. All movements are tagged with the current cashier’s
ID, and that can easily be circumvented with the copied db. Am I paranoid?

Thanks again for the help.

Yes, that gets me into the db; however, when I open the Linked Tables Manager, I ge an “Application-defined or object-defined error” message. Also, if I open one of the linked tables, I get the “Not a valid password” error again.

I can’t open the front-end because of the “Invalid password” error, so I can’t re-link to the back-end.

Food for thought! Thanks.

I set up a back-end, gave it a PW, closed it, and then opened the front-end. I get a “Not a valid password” error message opening the front-end.

The maintenance is a problem, but I can live with that. Is it possible for one of the cashiers to copy his db, change the password and name, and create an unauthorized user?

I don’t doubt it. It has been a long time since Nov 2005.

Could you look at my problem, in the meantime.

Just fine! Thanks.

Using NoMatch rather than EOF works. Does the unmatched FindNext stay on the last record found?

Thank you. Just one more point, please.

What happens if the error routine closes the procedure and neither a CommitTrans nor a Rollback command have been issued?

We are up and running satisfactorily. It was a good education. Thank you.

I will start a trial use of the code, as is, tomorrow. That should give me a better idea. I would like to be sure that a conflicting appointment on the first day of the series will not be allowed. That gives me the trouble of same starting dates and times, but different lengths, not being interpreted as a conflict. Can that be fixed?

This is getting complicated.

I added a form to pick up the starting and ending dates, and the length of the appointments.

When I check for conflicts in an appointment, the code recognizes as a conflict two appointments with the same start date and length. If the start date is the same, but the length is different, there is no conflict, and the code adds the new appointment. There is no awareness of appointments beyond the first date. I have played with changing the parameters for OutlookAppointments to pick up the ending date, but no help. I don’t understand the Set curAppt statement.

Could I show a conflict based only on the range of start date/end date, and not include the appointment length?

My example duplicates the appointment, and shows them side-be-side in the Outlook calendar.

How can I avert overwriting a previous appointment? The previous appointment could or could not have been set with this routine. If the appointment was set by the routine, there is a record in the table, but it only shows the initial appointment and not possible additional appointments using the interval specified.

Can you give me some ideas, please?

That did it! Thank you!

OK. Thanks.