CSD Tools

[millwheal]

On this site and elsewhere, I have read great things about Jeff Conrad's free software, CSD Tools.

I have downloaded and installed V2.0 of the software to use with Access 2003 under XP SP3.

Most things seem fine ... but when I try to create a report for Forms/Reports, I get "Error 3421 Data type conversion error".

This happens with every database I've tried, whether creating a report or using the Word or Excel options.

I have removed the software, downloaded afresh and reinstalled it, all to no avail.

Any ideas, anyone?

 

[RuralGuy]

Have you tried emailing Jeff?

 

[RuralGuy]

Mine works just fine on acXP and WinXP SP3.

 

[millwheal]

Rural Guy,

I don't have Jeff's email address, plus his site recommends asking questions via Newsgroup Help, but I'm not sure what that is, so asked the question here as I've had some help from AWF members in the past.

As Jeff kindly supplies the software free, I don't expect him to provide support to any and all users.

 

[RuralGuy]

Try creating a new db and importing everything into it. Then run Jeff's tool again and try it.

 

[millwheal]

I had previously tried 'Compact & Repair' with no change in results.
I've now tried the new/import suggestion, but still get the same error.

 

[RuralGuy]

Hmm...out of suggestions right now. You stated it happens with *every* db you try. How about a new db with only one form and no reports?

 

[millwheal]

I have created a new database, and added only one object, a form with no data source, and I still get the 3421 error, whether I choose 'forms & reports' or 'forms only'.
I also tried with just a single report in the database and got the same results.

 

[RuralGuy]

I'll see if I can get some assistance with this problem.

 

[boblarson]

Any ideas, anyone?

What service pack level are you on for Access 2003?

 

[AccessJunkie]

Hi,

This is very odd indeed. I've never personally seen that error nor has anyone reported that error to me when running the tool. I'm a little stumped at the moment.

Some quick questions.
1. What service pack do you have for Access 2003 as Bob mentioned?
2. If you open a report in your database, select Print Preview, and then print do you have any errors?
3. Do you have a default printer installed?
4. Are all tables in your database JET tables/JET link tables, or are you connecting to different sources?

--------------------
Jeff Conrad - Access Junkie - MVP Alumnus
SDET II - Access Test Team - Microsoft Corporation

Co-author - Microsoft Office Access 2007 Inside Out
Presenter - Microsoft Access 2007 Essentials
http://www.accessmvp.com/JConrad/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com

----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.mspx
----------

 

[millwheal]

In answer to Jeff's questions:

1. It's Access 2003 SP3.

2. I have quite a few reports that I have set to preview, and that I then print without problems.

3. Yes, there is a default printer specified.

4. In some databases, I have a few linked tables, but most tables are 'native'. NB The problem also occurred with two test databases I created [one with a single form, one with a single report, neither with any tables].

 

[RuralGuy]

Your description of the issue sure makes it appear to be some setting in Windows that is causing the problem.

 

[boblarson]

If Office 2003 SP3, then perhaps you need one of the additional hotfixes.

 

[millwheal]

I have now tried again on a different PC.
As far as I am aware, both Windows and Access are set up the same on this and the original PC, both being up to date.
However, on the 'new' PC, CSD Tools works for Forms and Reports!
The challenge I now have is to find what might be different between the two PCs, but in the short term, I can use the software by taking a copy of the database on which I particularly want to run CSD Tools to the 'new' PC and running it there. This is not a perfect solution, but it will get me what I want in the short term.
Thanks to everyone who helped.

 

[RuralGuy]

Good luck at tracking it down and thanks for posting back with an update.

 

[AccessJunkie]

Thanks for the update on this.

I've been trying to repro this issue in-house and have been asking around the team, but at the moment, I'm a little stumped as to why that specific PC is not able to run CSD Tools. If you find out any more information, please feel free to pass it along.

--------------------
Jeff Conrad - Access Junkie - MVP Alumnus
SDET II - Access Test Team - Microsoft Corporation

Co-author - Microsoft Office Access 2007 Inside Out
Presenter - Microsoft Access 2007 Essentials
http://www.accessmvp.com/JConrad/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com

----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.mspx
----------