Search results

Oops, sorry. Remove the Exit Sub from each of the Case statements. I forgot and left those in there.

Is your control visible when you try to set the value? It needs to be. I just got the same error if I set its visible property to NO.

Dick: He's telling you that she, using that computer she currently has, can connect to her own computer at home directly by using Remote Desktop Protocal (RDP). Read this to find out how: http://windows.microsoft.com/en-us/windows/connect-using-remote-desktop-connection

What version of Access are you using? I tried it in Access 2007 and this worked: Me.MonthView3.value = Date (my control is named MonthView3)

I've fixed it and have combined the two searches into one. Post back if you have questions. I took the input mask and validaton off. Those aren't good for searches.

I suggest uploading a copy of your database (with bogus data) so we can see what is happening. If you do remember to run Compact and Repair first and then ZIP the file before uploading.

You still didn't get it. If DCount("*", "tblUser","[PayrollID] LIKE '" & Me.txtPayrollIDSearch & "*'") > 0 Then

The problem is Access doesn't like BigInt. Have you tried using the SQL Native Client 10 ODBC driver?

Add an Action of DoEvents before this step.

You wrote: Forms!Referrals!Paycode = str_Paycode But where and what is str_Paycode? Is it a variable? If so, does the form Referrals have the field Paycode in its record source and you might need to just reselect it to make it work. Shouldn't have to but sometimes Access does weird things.

Your first query is correct but an Input box returns TEXT so you have to encapsulate that in the CDate as well.

Interesting way to get the output from a single function call. Never seen that done before like that. But my normal way is to make it more reusable so that it matters not how many parts you have. If you pass it 4 or 30, it would still work. Public Function SplitVal(strIn As String...

Yes, that is true about the SQL Functions. And, while the 2013 Web databases are more functional and can create more complex ones than one could in 2010, they are seriously limited. I wonder if MS will ever get it right. But then again, maybe if one needs a more complex one, ASP.NET would...

Gary - looks like you are missing a slight bit of code to move next. rs.MoveNext otherwise it will just hang there on the one record and be in an infinite loop since it will never get to the EOF.

The one problem with Web databases are that you need to use calculated columns essentially because there are things they can't do which one would normally do otherwise. I don't use web databases so it doesn't affect me and therefore I don't remember all of the appropriate caveats.

Maybe this will help: http://www.btabdevelopment.com/ts/removelookups You don't need to start over really but you shouldn't be working directly in tables anyway. You should have forms for the users, if you don't.

Not me....

I would not use lookups directly at table level if you are doing so. It would be best to use lookups at form level. Here's a link to more about why: http://www.mvps.org/access/lookupfields.htm

Just open the other form like this: DoCmd.OpenForm "FormNameHere", WhereCondition:="[SSN]=" & Me.SSN

If you delete data from linked tables, then that same data will be gone for everyone else, but only you know whether that is a problem for you as we don't know your business, etc.