L
Lungta
help! my 4 identical copies behave differently on other users' pcs.
The forms, buttons & word merge docs (A. Kallal Word Merge) all worked great
on my home computer yesterday. Copied the db on a disc & pasted onto my
desktop this morning, as always. I made 3 identical copies - one for the
network folder, one more backup and one to split.
The original copy from disc onto my desktop works great - the merge prompt
to select the document shows up right away & everything's fine. The 2nd copy,
same name, on network folder, doesn't work (all testing until yesterday was
done back & forth between desktop & this network folder so that's weird for a
start). The split version works great for me (FE on my desktop, BE in this
network folder.
But nobody else can get any of these to work - dbs all function properly,
reports print ok, but on word merge they keep getting "no data was created
for this merge; make sure the sql is correct", then it displays the same sql
that works fine in the other copies.
The following were verified on the other pcs: DAO 3.6 library, Word 11.0
just in case, Word set to "confirm conversion on open", default format Access
2k, run permissions "owner". Home computer is Windows XP running A2002, work
pcs are all Windows XP running Access 2003, db is still in Access2k format.
The code in question if you need it is:
Private Sub cmdMergeAll_Click()
strSQL = "select * from qryNotifLetters WHERE ApptID =" & [ApptID]
'note: the last [ApptID] references the field not the form control
Me.Refresh
MergeAllWord strSQL, ("word\Caseworker\")
'Note that you could use a condition in the above sql
End Sub
plus the WordCode module as per Kallal's original sample db.
This db doesn't have security or usergroups yet. An old version was split
for training purposes and workgroup security added, then all those shortcuts
etc. deleted. But if some of these don't even work for me, I'm assuming
workgroup levels aren't the culprit. Is it possible some old setting is
transferring to these new copies, or can anyone suggest what might be
happening? It's seeming a little weird around here, even for a full moon.
Thanks for any help you can offer!
The forms, buttons & word merge docs (A. Kallal Word Merge) all worked great
on my home computer yesterday. Copied the db on a disc & pasted onto my
desktop this morning, as always. I made 3 identical copies - one for the
network folder, one more backup and one to split.
The original copy from disc onto my desktop works great - the merge prompt
to select the document shows up right away & everything's fine. The 2nd copy,
same name, on network folder, doesn't work (all testing until yesterday was
done back & forth between desktop & this network folder so that's weird for a
start). The split version works great for me (FE on my desktop, BE in this
network folder.
But nobody else can get any of these to work - dbs all function properly,
reports print ok, but on word merge they keep getting "no data was created
for this merge; make sure the sql is correct", then it displays the same sql
that works fine in the other copies.
The following were verified on the other pcs: DAO 3.6 library, Word 11.0
just in case, Word set to "confirm conversion on open", default format Access
2k, run permissions "owner". Home computer is Windows XP running A2002, work
pcs are all Windows XP running Access 2003, db is still in Access2k format.
The code in question if you need it is:
Private Sub cmdMergeAll_Click()
strSQL = "select * from qryNotifLetters WHERE ApptID =" & [ApptID]
'note: the last [ApptID] references the field not the form control
Me.Refresh
MergeAllWord strSQL, ("word\Caseworker\")
'Note that you could use a condition in the above sql
End Sub
plus the WordCode module as per Kallal's original sample db.
This db doesn't have security or usergroups yet. An old version was split
for training purposes and workgroup security added, then all those shortcuts
etc. deleted. But if some of these don't even work for me, I'm assuming
workgroup levels aren't the culprit. Is it possible some old setting is
transferring to these new copies, or can anyone suggest what might be
happening? It's seeming a little weird around here, even for a full moon.
Thanks for any help you can offer!