Search results for query: *

I want to be able to send an Access report to a printer that automatically attaches and Acrobat PDF to the end of the report. In this simple example, I have a form letter that I want to generate from Access and have a 2-page PDF go with it as one job so our printer/stapler will treat it as...

Thank you for taking the time to reply on this! Yes, creating another report might solve the problem, but I wanted something more flexible.. and solving problems the code way is always more fun. ;) I'll give it a shot.

Well, it would, but it would only produce as many blank lines as there are records in the left-join table. That's the problem, because the end-user is ASKED how many blank lines they want.

This may seem like a weird scenario, but here it goes. I have a one-to-many relationship with two tables, where there may, on occasion, be no records in the many, and I want to pick up on that circumstance and print a seperate report for the user to print a report (actually a hand-fill-in form)...

Thank you very much everyone! I think I have a grasp on this now. ;)

Okay, so say I wanted to APPEND a new record? Would I use a similar approach, only changing the recordset method?

This is probably a really stupid question, but I want to commit values to a table for a record that is already partially populated, without using a form and VBA code only. I have no problems coming up with the values I want, but without using a form to bring focus to the record I want to...

I've worked with forms and creating coded links to picture files (jpegs), (rather than bloating my db with OLE objects), and it works pretty well, however, I'm not sure how to print those linked pictures in a report?? Namely, the problem is, that there is no place to trigger code to update the...

Nevermind.. I see that it's 1440 twips per inch. Thanks for your help. Everything works perfectly now!

Is there a quick and dirty way to print multiple copies of the same report without using a code counter (do/while)? What I'd like to do is have a field on a form with a "number of copies" to be used to print that many copies of the report.

Cool! That works. Now, does anyone know how many twips there are in an inch?

I have a report that I want to be able to change the layout via code, from data supplied from a table. I'm trying to change the top/left positing of the report fields on the fly to meet the demands specified in a parameter table. It doesn't appear there are any field positioning controls that...

I have a report that I want to be able to change the layout via code, from data supplied from a table. I'm trying to change the top/left positing of the report fields on the fly to meet the demands specified in a parameter table. It doesn't appear there are any field positioning controls that...

Use the Jet Compact utility. This handy little program lets you rebuild corrupt databases created in Access that Access' own compact and repair function won't. I have a copy of it if you need. I'm sure it was a freebee, but I can't remember where I originally got it.

You could probably code for it using the shell function, but another idea would be to link the tables in the databases you want into a central location. That's what I've done for my uses in having all the data centrally located.

That's exactly what I tried in the first place (see initial post above). It just returns the name of the field, not the value of the field.

If [forms]![formname]![numberfield] is 2 then with your syntax, it's returning: [2] Apparently ignoring the ItemType and assuming it is a field itself. What I want the select statement to yield is ValueField: [ItemType2] Where, the form's field value is assertained as being 2

Since you have it split in two, I would start with the frontend and import all objects in the frontend. I have seen problems that showed up later down the road from converted databases. Especially with things like code not running or attaching to controls on forms, etc. The reimport into a...

XP is a memory hog compared to 98 and with only a 35% increase in RAM in the migration, I would suspect you would see more problems, not less. XP is by nature, far more stable, but non memory-prudent. You must have an enormous control base to have memory problems with 98 and 384MB of RAM...

I've run into this a few times before. I was able able to get things working with a reimport into a blank database, but I also noticed I haven't seen any recurrences of this since Office2k SR1-SP2. Might be coincidental, but if you're not up to date, it might be worth a stab.