Search results

Now that's interesting. I ran it against my example of Smith, George B. Using Smith, George B as the input against the table that had it as Smith, George it showed a score of 1. Matching exact name against exact name of course scores 0. If I match the other way around it shows me 2.2. Which...

yeah, I don't control both tables, only one. the other comes in on a regular basis that I import. i tried the example - it just gave a null value in return.

Thank you, that wasn't what I was asking. In other words, tblPhone may have a user named Smith, George B and if I try to compare it against tblUsers who also has him but listed as Smith, George it won't match. An easy way to think is to do it in reverse but not possible as i'm trying to...

When trying to match people's names - sometimes with a middle initial, sometimes without - I'd like to try to wildcard each side of it. So this varProblem = DLookup("EMAIL_ADDRESS", "tblUsers", "EMPLOYEE_NAME Like '" & varString & "*'") but also something like this. varProblem =...

been giving it some thought. I'm thinking the result would be the same. I could just as easily assign a dim to what's passed via the txtUserID. What I probably need to do is unbound the form and set each location that calls it to do it via vba instead of macro.

hmm, i haven't used that yet. let me research into it.

Same error - missing expression, which works fine doing a macro open.

I have a bound form that normally is opened via macro. Very straight forward just has the following in the where. [userID]=[Forms]![Home]![txtSelectUser]I'm trying to open the same form via doCmd. DoCmd.OpenForm "frmUserInformation", , , "UserID=" & Me.txtProblemIDI've msgbox'd the...

I probably can't offer much more at this point. Only alternate way I can think of is to use the same table. meaning it launches - inserts whatever information desired into one temporary table that is later used as the source of the report.

I had a very similar situation. I tried to print to word after having a report open. I finally switched directions and had a button just make the report via VBA. This thread details out my woe's, rookiness and some fantastic help I got printing out to word...

That worked out really well. In the event someone else stumbles here - i used the following on my onLoad event for the form. Dim strInformationString As String If Not IsNull([fldSystems]) Then strInformationString = Trim([fldSystems]) Me.txtSystems.RowSource = strInformationString...

what is your desired output format - pdf, word, excel?

The textbox on the User Information form that I'm referring to is txtSystems - in it would display the systems the user frequently uses. For example. Mary, Jane, Jean - use sysInfant Grace, Chris, Pat use sysToddler .... Charles being a floating employee could use sysInfant, sysToddler or...

In my Access 2013 Database I have a form for user information "frmUserInformation" (stored in tblusers) normal details are in there, last name, first name, etc. I have a related table for user submissions and other submissions both tied back to the user id in tblUsers. All normal everyday...

actually I was completely wrong in my assumption. What it was was the needed reference to the word object when setting InchesToPoints. This 'set column widths oTable.Columns(1).Width = InchesToPoints(1.75) oTable.Columns(2).Width = InchesToPoints(0.8) oTable.Columns(3).Width =...

I've narrowed the problem down. It's farting in a similar manner as my original post when also trying to use Rx's code. The problem specifically is when you create rows in the table then enter a recordset loop to create more rows. Or vice versa if you create rows in the loop and later try...

yours is definitely working. I'll have to step through yours and mine and see what's up. or more likely rebuild mine.

When I run this code to create a word doc - the first time no problem. Second time it pops the Error 462 error. Research on it shows it's usually when ActiveDocument is referenced without specifying the word.Application first. All that is fine I only have that in one location and it's...

Seems to keep producing the extra rows for each record in the repeating field. I may have figured a way to get it to work - taking the results, combining the repeating row into one cell then save it to a table and pull the report off that table. Working through quirks for now.

I'm assuming trying to populate it with VBA is a futile effort?