Luke,
I have the greatest respect for you and your company. You've mad VBA
development more than just a sideline. I actually make money doing it.
I'm not even sure which package I bought. It came with about 5 modules and
cost $1,000 for my single seat. I installed it on my client's development
machine (I use it through Remote Desktop). I used the procedure generator the
most. It did a good job of producing a good shell, but I felt it could have
been enhanced to produce more content. As it was, it was mostly
documentation. But, I did use it.
The database documentor did not run well on the development machine. The
first few times I ran it (just "playing",) I had at least one instance where
it just "hung" and I had to have my client do a hard reset of the machine. I
did get it to run once, successfully, but the report was so voluminous I had
trouble culling the important from the "nice-to-have" information. I used it
to correct a couple of poor coding practices.
I sat down to read the docs that came with the software, and did so--I
read docs...
I felt like they were formatted versions of the online help screens. Didn't
add a lot of "why would you do this..." to the mix.
I never used any of the other mods, and then, as I said, my client
suddenly decided to go to A2007, obsoleting my package on the spot. I
continued to use the procedure-generator for awhile, but eventually
deinstalled it when some other problem needed debugging and I suspected FMS
tools (logically, since they were not designed for A2007...)
Total Access Emailer would be of interest, but my client is yet only
tiptoe-ing into the email waters. I did try to get fancy and "look up"
information from the Outlook (2007) contact list while assembling documents.
It took 15 minutes to connect to the object. I gave up that idea quickly.
Again, I appreciate that you care. Thank you for continuing to legitimize
Access development.
Jim
--
Jim
Luke Chung-FMS said:
Hi Jim,
Sorry our tools didn't meet your needs. I would appreciate any feedback on
which products and documentation you found lacking.
As for Total Access Emailer, we have a large number of customers who have
found it to be very useful for their needs to distribute filtered reports to
each of their contacts. If you're not familiar with it, we have a demo
version that lets you send out emails with it.
Luke Chung
FMS President
http://www.fmsinc.com
JimS said:
I've been marginally unimpressed with FMS tools. They generally work, but
with their sparse docs and high price, I found myself trying things that
failed spectacularly, costing me time and stress. And then, my client moved
to A2007 (with no notice). I'm not up for paying again, so I'm not using them
anymore.
Thanx again!
--
Jim
S.Clark said:
Philosophically, it was as painful for me to recommend as it was for you to
implement it.
But given the constraints involved with the SendObject
methodology, it's the right tool for the job.
Alternatively, there is the FMS Total Access Emailer.
http://www.fmsinc.com/MicrosoftAccess/Email.asp
:
Well, I had a philosophical issue with doing that, but it worked so well,
I've put aside the notion that the report should be more generic and moved
on. Thanks.
--
Jim
:
Add a parameter to the query that references the desired value from the form.
e.g. Forms![Formname]![ControlName]
:
I want to send a report via email. I realize there is no "wherecondition"
construct in the sendobject method. So, I've set the report to interrogate
his calling form. I'm having a couple issues:
1. The OnOpen event doesn't seem to fire in the sendobject process. That's
where I'd usually set the filter for the report.
2. Using the construct:
If CurrentProject.AllForms("sfmpicklistdetail").IsLoaded Then
I am referencing a subform that's on the main form that calls
sendobject method. Access doesn't seem to recognize it as loaded. Am I unable
to reference it like that?
