Recent content by dsfcom

Thanks Rookie. I will keep this in mind in future development. Good to know!

Yes...one db to another via Access2007 with Access2003 dbs (*.mdb). While fixing the fields I believe I may have found the problem. Some of my queries are based on tables that do not always exist and from reading related posts it seems this may be causing my issue. Does this seem likely?

I am having some trouble with importation of queries which exhibits seemingly random occurences of query fields being renamed to "Expr1: [FieldName]" after import. [FieldName] references the original field name Does this occur because of the import process? There were no users connected...

Just a quick question concerning this thread...what type of field is in 'tblHolidays'? Is it a date containing a full date or a text containing only the month/day? Also, i'm trying to use thte same function and calling it from a different function with: fNetWorkdays(strStartDt, strEndDt...

That question was also in my post...any offers for a solution? This works to get the first name only from the [FIRSTNAME] [MI] combination even if there is no middle initial: FIRSTNAME: IIf(Left([FIRSTNAMEMI],(InStr(1,[FIRSTNAMEMI]," ")))="...

Thanks for the update and learning session!

Hello. I've learned a bit about breaking down text strings today but am still having some trouble with splitting a text field using a query. My field contains either [LASTNAME] [FIRSTNAME] [MI] or [LASTNAME] [FIRSTNAME] combinations. What I'm trying to do is break down the field into three...

You've proved my point John. I was having age miscalculations because of that single day deviation and came across another method that seems to work a little more accurately for now.

I was using a formula similar to yours John but it doesn't calculate the age correctly for all given dates I've found. The formula below actually seems to work "accurately" for all given dates and provides an accurate age...

Try what is mentioned in post #4. Add the OnOpen/OnLoad event to the report and it will output itself to pdf when it's opened.

Not sure what you mean by "embedded macro", but if you need to run a macro via code use a line like this: DoCmd.RunMacro "mcrThisMacro.mnThisName" To output the report via code only, add something like this to your report's OnLoad or OnOpen event: DoCmd.OutputTo acOutputReport, "rptName"...

Not sure about this but is the query updateable? I've used similar lines in the past with queries exactly as you have them with no problems. Never tried it with a query that's not updateable. Maybe you need an "rsEmail.MoveFirst" in there after you set rsEmail? But if you're having trouble...

In your macro conditions column put something like: [Forms]![frmThisForm]![claimID] = [Forms]![frmClaimsParts]![claimID] Your code portion looks a little ambiguous. You're assigning a value to strCriteria that's assigning a value to [claimID] and that won't work. Assign the value of your...

You should be able to create one query using both tables. Join them by the unique field (whatever it is; say [FACID]) and then add the fields you need to the query and group sum the pay data. The fewer fields added the better so it will sum properly.

Send some sample data and a few specs and we'll see what we can do.