Quote Originally Posted by nickjf89 View Post
... I'm gutted that I finally finished the hard part, and the easiest yet most important part of testing and making it available to the people who want it is causing me hige problems
This is a huge misapprehension.

Deployment is a complex subject and there is no magic bullet out there for it. There are lots of issues involved that vary with each application. People make some good money helping people properly package applications for deployment.


Here I would hazard a guess that you have bulled ahead ignoring one of the design issues you need to address before writing a line of code. It looks like a common one we see here often though: You didn't think about your application's deployed footprint. Don't feel bad, people who have been hacking away for years (sometimes paid for it) do the same sort of thing.

An application's footprint includes a number of things, but the most relevant one is to avoid putting read/write data files and registry keys into protected locations.

Let me guess: You put this .SDF file or files under Program Files/Programs.

People often ran XP systems logged on as admin all day long, or they left critical directories unsecured in the manner of Win9x. That was then (2001) and this is now (2007 and later) and current versions of Windows are not as forgiving.


There could be connection management issues that might cause the same error, but that's my guess based on the limited information provided.

Look for a FAQ here on the subject and its resolution.