D
diarmuidq
I realise this problem is as old as the hills, but still I'm a bit confused.
Spent all day researching this, but I'm confused about the best option. I
have Office 2000, and have the Office developer tools. And everything else
that comes with MSDN.All of my customers are using at least Windows 2000.
On most sites I get one of these two problems:
1) Date() or Left() or whatever not working. A remove, add reference
followed by a recompile usually fixes this. From reading the famed
http://www.trigeminal.com/usenet/usenet026.asp there seems to be several
steps I can take to prevent this.
a) One is to replace Date() with VBA.Date(). Which is fine in my code,
except I can't seem to get that to work in queries. For example, the
criteria won't except >VBA.Date()
b) Late binding the references. That is, no ticks on my References, declare
the objects through code. This seemed a bit complex, but I didn't really try
as I distribute mdes and this method only works with mdbs. Btw, any one got
a sample database that uses this late binding?
2) Missing or broken reference to comdlg32.ocx
Caused by comdlg32 not being registered on the target PC. Theres a method
for registering the dll through code, but again it seems only to work for
mdbs.
Is a setup package the best way around this? Or should I change to mdbs, and
use the reference coding?
Thanks
Diarmuid
Spent all day researching this, but I'm confused about the best option. I
have Office 2000, and have the Office developer tools. And everything else
that comes with MSDN.All of my customers are using at least Windows 2000.
On most sites I get one of these two problems:
1) Date() or Left() or whatever not working. A remove, add reference
followed by a recompile usually fixes this. From reading the famed
http://www.trigeminal.com/usenet/usenet026.asp there seems to be several
steps I can take to prevent this.
a) One is to replace Date() with VBA.Date(). Which is fine in my code,
except I can't seem to get that to work in queries. For example, the
criteria won't except >VBA.Date()
b) Late binding the references. That is, no ticks on my References, declare
the objects through code. This seemed a bit complex, but I didn't really try
as I distribute mdes and this method only works with mdbs. Btw, any one got
a sample database that uses this late binding?
2) Missing or broken reference to comdlg32.ocx
Caused by comdlg32 not being registered on the target PC. Theres a method
for registering the dll through code, but again it seems only to work for
mdbs.
Is a setup package the best way around this? Or should I change to mdbs, and
use the reference coding?
Thanks
Diarmuid