Developer Kit – Common Problems and FAQ’s

Developer Kit – Common Problems and FAQ’s
Kit 1’s SLPAPI32.DLL is reported to be corrupt by my compiler.

This resource is compiled with Borland C and not Microsoft Visual C++. Although environment settings can be made to enable link to this resource at compile time, it is recommended that you explicitly load this resource from your program. This should eliminate compiler dependency and make the functions accessible to programs regardless of what Windows 32 bit programming language is being used.

Kit 1 reports missing DLL’s

This High Level API relies on DLL’s that are shared with the Smart Label application. These are installed automatically during the Smart Label application installation. Optionally, you can download a utility to install only the files required by the high level developer kit.

Other Hints

Are all resources spelled correctly. Note that these are often case sensitive.

Note that Kit 1 and Kit 2 both contain DLL’s bearing the name SLPAPI32.DLL. These are not the same and cannot be used concurrently (due to their sharing the same name.) A subsequent developer tool kit set will likely rename one or the other of these separate resources.