First check for the existence of {db_name}.ldb.
Does it exist? If so, attempt to delete it. If you get a sharing violation, then some other process really does have the database open (perhaps a backup program?)
If you are able to delete the ldb, see if that fixes your problem.
Thsnks for the advice, but it didn't do the trick. After saving, the Word 2.0 document is still in the 2.0 format.
If I save it manually in Word (10.0), Word asks me if I want to preserve the original file format or overwrite it in the current Word format. That's what I'm trying to automate.
I have Word 2.0 documents that I would like to programmatically resave in the current (Word 97 and beyond) Word format. I've tried capturing the "do you want to save this 2.0 docu..." dialog in a macro, but that didn't work.
Maybe this isn't something you can do in VBA?
Users must be granted delete rights. If not, the ldb will eventually fill up to its maximum of 255 entries and no one will be able to open the database.
It may be uncomfortable, but you must grant both Create and Delete rights to all users who share an Access database. This is true for both...
Do you get the error running on the same development machine, or only when run on a different workstation? I've seen this caused by version mismatches in DLL sets.
What is the OS? (W2K prior to SP1 has a problem that results in the error message you report)
Which line raises the error?
The...
SendKeys can only plase keycodes into the current program's keyin buffer, it doesn't work across processes. Even though the shell is opened from within your program, it's still running in its own process space.
If you're using DAO, begin/commit/rollback are methods of the workspace object.
Be aware that transactions are more limited in Access than in many other databases such as SQL Server. You cannot roll back a record deletion or DDL, for example.
Consider implementing your own row-locking scheme. Add a boolean field to the table that indicates a row is locked, and put the read/write permission logic in your application code.
Don't use a dynaset-type recordset when editing data - use a forward-only snapshot-type recordset, then build a...
If you're using DAO, just rename the database's extension; DAO doesn't care what you call the database.
Be careful to choose an extension that isn't already registered with another application -- a user may double-click on its icon and open it in Photoshop or something, and totally trash the...
If you are writing significant end-user applications that are primarily front-ends for a database, VB is the way to go, hands down.
What you can't do with VB is write small, lean utilities that don't require a lot of dependent files. You also can't write code that can be ported to non-Windows...
Try putting a DoEvents in your do-while loop. It may not solve your printing problem, but at least you'll be able to provide a way to close your app without resorting to the Task Manager.
What happens if you take that loop out altogether? Does the .PrintOut method not block until the document...
Make sure you have the TEMP and TMP environment variables defined (My Computer -> Properties -> Advanced tab -> System Variables)
This is just one of probably many causes for this generic error.
In my opinion, it is irresponsible for us to go around dropping mystery keys into people's registries that never get cleaned up. Bad idea.
Here's a suggestion. You give the user a key which has the expiration date encrypted into it. On first run you save the key so they don't have to type it...
Your problem is probably not directly related to Crystal Reports. What you're describing is a classic symptom of a COM object that was never set to Nothing, and that's what is keeping your exe from unloading.
Make sure that all objects are set to Nothing when you're done with them.
Your code is probably not responsible for this error.
What's happened is Jet momentarily lost connection to the server. Windows can recover from such a burp, but Jet doesn't seem to be able to.
If you see this error often on a specific workstation, you may have a cabling problem. Or a crappy...
Question: has your database been nearly that big for quite a while, or did it suddenly grow to such an enormous size?
I've seen corrupt databases balloon by 50% per day until it was fixed. I saw a 16Mb database become 100Mb in less than a week.
How did you implement your autonumbers?
I presume it is no longer an Access database, and they created a SQL Server database with the same design. That would have involved changing Access Counter fields to SQL Server Identity columns. That should have worked OK.
However, if you are using...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.