| T O P I C R E V I E W |
| hergal79 |
Posted - 24 Aug 2015 : 15:16:39
I seem to have reached the limit of the version of 32-bit program (1952 movies and a few series). I get lots of error messages about limit is reached. The problem is I can not do anything because I can not save the database after delete / edit movies. I get the message: "Error saving database. Code: 23-5-La generación SOL dinámica para DeleteCommand no es compatible con SelectCommand. que no devuelve ninguna información para columnas claves..."
Which in English would be something like: "Error saving database Code. 23-5-SOL Dynamic generation DeleteCommand is not supported against a SelectCommand that does not return any information for key columns ...."
Where I can download the latest 64-bit version?
Any other suggestions?
Sorry for the english, I used Google Translate.
Thanks |
| 15 L A T E S T R E P L I E S (Newest First) |
| hergal79 |
Posted - 29 Aug 2015 : 17:30:10
I finished installing the 64-bit and still have the same problem, can not save the database. Same error message.
I have to clarify that the "example" database have no problem saving, it is something from my database.
http://imgur.com/QEALrli
Now when I select many of the movies of my database, no data appear and not cover (as in the picture), I get the message: "can not access the information removed from a row".
With this version 32 this does not happen.
|
| alsystems |
Posted - 28 Aug 2015 : 09:36:08
You might want to look at past discussions about 'Out of Memory' problems in XMM:
http://www.binaryworks.it/forum/topic.asp?TOPIC_ID=13304
http://www.binaryworks.it/forum/topic.asp?TOPIC_ID=11321
My own XMM database has now reached has the limits of XMM 32-Bit:
900MB for MDB File
(3318 Movies, 55097 People)
32-Bit Access is supposed to have a 1GB File Limit but I have determined 900MB is probably the practical limit for an editable database in XMM.
I will have to start running XMM 8.4.2.0 64-Bit myself which has a 2GB File Limit. Since I use Open Office instead of MS Office, I can safely add the 64-Bit Access Database Engine without conflicts.
Maybe I just have to rewrite XMM myself in FileMaker which has a very generous 8TB File Limit. I still don't know why Microsoft Access still has a 1 or 2 GB File Limit today when multi Terabyte drives are the norm. I believe it was 20 years ago that Microsoft fixed the old 2GB partition limit on hard drives. But apparently MS Office never fixed a similar limit in Access. There is no excuse for this oversight that glares as brightly as a supernova.
|
| hergal79 |
Posted - 28 Aug 2015 : 05:24:12
It may be that I have installed 64-bit version of Office running at 32-bit? Because if not, there is something strange or wrong what you say because the XMM 32 works.
This weekend I will try with 64 bits. |
| alsystems |
Posted - 27 Aug 2015 : 18:16:30
Don't forget to make sure you have the 64-Bit Access Database Engine installed when using the 64-Bit XMM database. If you are already running 64-Bit Office (with Access), you probably already have it installed.
The 32-Bit XMM won't run with the 64-Bit Access Database Engine installed. Microsoft allows installation of only one Database Engine at one time (64-Bit or 32-Bit). |
| hergal79 |
Posted - 27 Aug 2015 : 09:36:29
It is the same version that I could find searching the Web. I still could not test it, any problems I ask you.
Thanks! |
| alsystems |
Posted - 27 Aug 2015 : 06:19:33
I have a copy of XMM 8.4.2.0 (64-Bit) if you want to try that one. It should be able to handle a 2GB MDB file. |
| JDommi |
Posted - 26 Aug 2015 : 13:29:13
I still use Office 2003. Therefor XMM 32-bit. |
| hergal79 |
Posted - 26 Aug 2015 : 03:31:40
I have the 64-bit Office 2010 and I can not open the database in Access. I receive hundreds of messages like: "id" is not an index in this table; "ParentIdName" is not an index in this table, etc. Which version of Office do you have?
The only way I can think* to modify the database is to download an old 64-bit version of XMM, the 32-bit version refuses any change.
* Or export to excel, import to a new database in XMM and re download all data from IMDb, but it is very tedious.
|
| JDommi |
Posted - 26 Aug 2015 : 02:43:49
Sorry for late reply...
I still use the 32-bit version under Win7 - 64 bit. So I have the compact & repair function working. But 'til now I never have to have used it.
For me I have restricted IMDb to download only 12 actors as more are useless for me. Otherwise I would use the directlink to open the IMDB site.
If I would use the 64-bit office version I always would open the mdb directly with Access and use the function from within there.
To remove all actors you can also use Access directly. Open the database and remove all entries in the persons table or mybe only a few fields. If you remove every person you have to clear the actors, directors, writers, ... fields in the movies' table, too.
This way you have the chance to open the database even if XMM refuses any changes. |
| alsystems |
Posted - 25 Aug 2015 : 20:27:18
Hergal79,
I've set the actors to a maximum of 20 for each movie except for a few mini series which I've set to 50 instead. This has allowed my movie list to contain twice the number yours XMM database has. However our MDB filesizes are almost the same. Although 20 Actors is not a standard option on the IMDB.com (Complete) script, I've modified the script to do this.
I think the only way you might reduce your database to a size that still works, is to reduce the number of actors attached to each movie. It might take a lot of work and certainly start with a good backup first. Either start removing some actors one by one in the Actor Table or perhaps delete them all and let XMM Re-Update your movie list after changing the script option for maximum number of actors.
For this to work, you would have to start with a backup database that still worked, since your current copy is unusable. |
| hergal79 |
Posted - 25 Aug 2015 : 05:47:57
quote:
What is the size of your mdb file, hegal79? Mine is currently 899MB (contains 3310 Movies) and still works with the 32bit XMM version. But I believe it is close the limit. The database has crashed occasionally.
908MB.
The compact and repair function I used it often because for some time the XMM had problems (crashes). With this function the problems were reduced.
Now, compact and repair is useless.
I think it was a big mistake to import 999 actors in every movie... |
| alsystems |
Posted - 24 Aug 2015 : 23:49:26
JDommi,
If you have a 64Bit Access Database (XMM) that gets corrupted, what are you supposed to do with it?
I needed to use the 'Compact and Repair' function about four times on my 32 Bit XMM database already. |
| JDommi |
Posted - 24 Aug 2015 : 19:27:26
quote:
Originally posted by alsystems
I too would like a 64Bit version of XMM. I believe the problems is that the 'Compact and Repair' Database Function would erase the entire database instead of repairing it on the last version. I don't understand why it is difficult to get a system function working?
Because the 64-bit driver does not provide this function and as far as I know nobody has managed it yet to get this function working. |
| alsystems |
Posted - 24 Aug 2015 : 19:11:46
quote:
Originally posted by hergal79
I seem to have reached the limit of the version of 32-bit program (1952 movies and a few series).
What is the size of your mdb file, hegal79? Mine is currently 899MB (contains 3310 Movies) and still works with the 32bit XMM version. But I believe it is close the limit. The database has crashed occasionally.
I too would like a 64Bit version of XMM. I believe the problems is that the 'Compact and Repair' Database Function would erase the entire database instead of repairing it on the last version. I don't understand why it is difficult to get a system function working? |
| JDommi |
Posted - 24 Aug 2015 : 15:41:37
I have forwarded your question to Ale, as I can't say anything to that. |
