Search results for query: *

That did it. It works great Cheers

I have a form called 'Occurrences' with a subForm called 'OccurrencesSub'. On the form I have two fields, one is called 'Begin' date and the other is called 'End' date. The user may enter the beginning and ending dates directly into the fields or select an option button what will populate the...

Thank you very much for the response. Can you explain the significance of the word 'TYPED in the first line? I'm not as well versed in access as I should be but I copied the text into a command button on the main form and substituted the sub form name (Frm_SoldSub) into the third line. It...

I have a form with a subform. The subform is a continuous form. The number of records displayed in the subform always varies. I am attempting to build a button in the main form that when selected would add info into a selected field of each record in the subform. This is a sales/inventory...

I have three printers (one laser, one inkjet and one dot matrix). It doesn't matter what printer I use, the 'page setup' WITHIN Access for that report will not allow me to decrease the margins. I can setup a page within Word and decrease the margins in page setup and the dot matrix will print...

I have developed a report in Access. This report is designed as a label. The label to be printed on a dot matrix printer with continuous form labels. The problem: I can't adjust the page margins in Page Setup. I want to change the top and side margins to "0" but it defaults to 15.8mm from the...

I wish I was smart enough to know what you are talking about. Sorry for being dumb. However, you said something that intrigued me. Let me try to answer your questions. 1. Yes these are sql linked tables. These tables were created by first building them in Access and then converting them to sql...

I am lost in no man's land. I have posted it on the SQL forum and they say they don't know because it is an Access problem. I posted it on the Access forum and they say they don't know becuse it is a SQL problem. Can someone please help?

I already have, They suggested I post here?

Gives me the same error message

I have tried that and it returns another error message: Run Time Error 2501 The DoCmd action was cancelled. I'm baffled?

I have tried several different delete methods but it makes no difference. They all return the same error message

I have a problem with deleting records. I have a form in my database where I have included a delete button. The delete function works perfectly with an access tables (backend). When I connect that same form to the converted SQL tables (backend) it gives me an error message: run time error '3146'...

I have a problem with deleting records. I have a form in my database where I have included a delete button. The delete function works perfectly with an access tables (backend). When I connect that same form to the converted SQL tables (backend) it gives me an error message: run time error '3146'...

Ok, here goes If Me![LeaveEnd] > (Me![BeginningDate] + 13) And Me![LeaveBegin] >= Me![BeginningDate] Then MsgBox [Title] & " " & [crewmember] & " has " & [LeaveType] & " on " & [LeaveBegin] & " to " & [LeaveEnd], vbInformation, "RACS" If Me![LeaveEnd] > (Me![BeginningDate] + 13) And...

I have been able to get the procedure to work. At first I used the code suggested by PHV and continued to replicate the code for each day combination, including repeating the msgbox for each day. I got the same error even when I split the code between AFTER UPDATE and ON CHANGE. I went back...

That loop worked well but by the time all possible combinations of dates are entered, I still get the "Procedure too large" error message. Even tried spliting the code betqween the 'After_Update' and the 'On_Change' and I still got the error.

What I have is a rostering database. When I select the employee to assign a shift, the procedure looks at the annual leave requests and displays "A/L" into that specific days roster. The code I have used is: If [LeaveEnd] > ([BeginningDate] + 13) Then If [LeaveBegin] = [BeginningDate] Then...

I have a large procedure with a number "if" statements. I get an error message that the "Procedure is too large". Is there anyway around this or do I have to reduce the size of the code?

YES. That did it. Thanks a lot. It worked perfect