This was working this morning and I had no problem. I've got two versions of the same database, and am trying to copy some updated objects (forms mostly) from one to the other. This was working this morning. Don't know what changed.
I am the only person in the database. I closed down all code windows. I tried while in design mode on a form, and not in design mode. Both talk to a split backend. One has a couple of local copies of tables that are linked on the source database.
Not sure what to check. I compacted and repaired the destination database too, that was giving the error, just in case some gremlins were hiding out.
I tried closing the source database, but it said it would empty the clipboard if I did that, and I would lose the object I was trying to copy. WORKED THIS MORNING, on another version of the database.
Any pointers? I checked several of the other posts with "database has been placed in a state" in their text, but nothing seemed to be on the money.
Looks like it had to do with trying to move from a 2002-2003 database to a more modern one. Others have had similar problems from this same situation.
Related
I'm working on a project that has some pretty specific requirements, and am running in to a problem with one of them. We have a locked SQLite database. We can't unlock this database, but need to read it (but not write to it), and we cannot create any new files on the filesystem that contain the data from this database. What was suggested is to read the file in to RAM, and then access it from there. I've been trying to find out a way to do this, but this project is on Windows, so it's not going as smoothly as it might otherwise.
What I've been trying to do is read the file in to a bash variable, and then pass that variable to sqlite as the database. This hasn't been working particularly well.
I installed win-bash, but when I do "sqlite3.exe <(cat <<<"$database")" I get a 'syntax error near unexpected token `<('" I checked, and win-bash looks like it's based on an older version of bash. I tried zsh, but it's saying "doesn't look like your system supports FIFOs.". I installed cygwin, which wouldn't really be a good solution anyway (once I figure out how to do this, I need to pass it off to our Qt developers so that they can roll it in to a Qt application) but I was just trying to do a 'proof of concept' - that didn't work either. Sqlite opened just fine, but when i ran ".tables", it said "Error: unable to open database "/dev/fd/63": unable to open database file" So, it looks like I'm barking up the wrong tree, and need to think of some other way to do this.
I guess my questions are, first, is it possible to read a sqlite database in a variable as I was attempting, or am I going down an entirely incorrect path there? Second - if it can't be done that way, is there some way I'm overlooking that might make this possible?
Thanks!
I have an out of memory error on access. My DB is approx 20mb and holds approx 100,000 lines in different tables.
It started this afternoon, whenever i go in the VBA editor, i can't edit anything, because it will delete the text i just typed, and popup "Out of memory".
If i try to use a OnUpdate event on a DropDown list, it will say the same error, and will do nothing. I can't even setup a break point on my code, because it will never go in the code.
I tried compacting it, separating the back and front end. but nothing works, same error. I'm on Windows Xp Sp3
Strange errors like this are sometimes caused by a corrupt form in your database. I would recommend trying to decompile the database file.
You can get more information about the /decompile switch from the following:
How to Decompile a Database
Decompile Your Microsoft Access Database
I would make a backup copy of the database, then do a decompile, and then a compact. Then open up the database and open your VBA Editor and Compile your code. Then test it.
The /decompile switch has fixed many strange problems with Microsoft Access databases for me in the past.
I'm working through the "Demo: Binding Data with the SqlDataSource" of this pluralsight video on ASP.NET Webforms.
All communication with the database works just fine, except it won't change when updates are made. The only thing I've done differently from the video is to use Northwind.sdf instead of Northwind.mdf. The database exists in the project directory, which is under my Users directory on win7 -- so it shouldn't be a permissions problem.
What could be preventing it from updating?
In case anyone wants to try the sample app, I uploaded the whole project folder here on mediafire.
Maybe you have two copies of the database. You are updating copy A and then checking copy B.
Or, it could be one of the reasons described here: http://weblogs.asp.net/stevewellens/archive/2009/10/16/why-sql-updates-fail-three-reasons.aspx
There appears to be a slight problem with my Livecycle server with regards to documents suddenly disappearing!
After looking around, it seems that the documents are not deleted completely, but moved to another folder ('livecycle\content\lccs_data\contentstore.deleted'). Thankfully these 'deleted' documents can simply be moved back to the contentstore. Livecycle's ContentServices uses Alfresco, and I found the following with regards to this automated deleting of documents:
http://wiki.alfresco.com/wiki/Content_Store_Configuration
For now, I will attempt to remove this functionality (removing the StoreCleaner's listener, so no action will be taken), but I'm unsure as to whether removing the finding of orphaned documents could be detremental to the system.
Is there anyone who knows exactly why the system is incorrectly flagging files as orphaned and then removing them? In the Livecycle adminui I can still see the documents that have been deleted, so at least the UI is still holding references to them.
I'm using LiveCycle quite a bit and no problem here. I'm doing custom Alfresco stuff all the place and no disappearing doc's here.
I guess there might be some custom rules/js LiveCycle process who flags the doc's. So check al these and try to analyze it more in depth, so we can help out.
Does they get deleted randomly, or just from specific folders, try to turn off the rules to check if it still happens.
And if it still occurs, just log a call at Adobe, you never know what Adobe has build in it ;)
The scenario is this. I have a SQL Server database online that I am demoing an application. During development, I have added extra fields, modified field types, changed keys and added some new tables locally.
What's the best way for me to update the online database with the new structure and not lose the data? The database is a SQL Server 2005 one.
Download a trial of Red Gate SQL Compare, compare your two servers and you are done. If you do this often, it is well worth the $400, or get one of their bundles for a better bang for the buck.
And I do not work for Red Gate, just a happy customer!
Write update scripts to modify your live database structure to the new structure, as well as inserting any data which is required.
You may find it necessary to use temporary tables to do this.
It's probably best if you test this process on a test environment, before running the scripts on the live environment.
Depending on what exactly you've done you may be able to get away with alter statements, though from the sounds of it (removing keys and whatnot) you're doing some heavy lifting that may make that a less-than-ideal solution. You should probably look into creating a maintenance plan or, better yet, a SQL Server Integration Services project in Visual Studio. You should be able to migrate the data in the existing database to a new one using those tools.
This probably isn't of huge help retrospectively, but I always script all structural DB changes to my development database and then using a version number to determine the current version of the DB I can run the required scripts on the live DB, hence bringing it back in line at the same time as the new code is uploaded.
This also works for any content changes, for instance if the change in the underlying structure has an effect on the conent stored you can also write scripts to migrate the data accordingly.
Make a copy of the existing database to copy from.
Make another copy and alter it to your new schema. save DDL for reuse.
Write queries that copy data from #1 to #2. Save the queries for reuse.
Check the results.
Repeat until done.