| Author |
 Topic  |
|
|
DrunkBell
New Member
Australia
74 Posts |
 Posted - 19 Nov 2014 : 14:45:10
|
I am updating with actors for 5 days now without any problem, until i figured that actors not created anymore to movies after 4763th movie, it says Cannot open database that your application recognizes or the file may be corrupted.
I started backup and repair, it finished without error but mdb file magically disappeared. There are 5510 movies with 162128 actors. MDB file size 2GB which i think it causes the problem.
Any advise please? |
 |
|
|
Mawu
Senior Member
Germany
1028 Posts |
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 19 Nov 2014 : 16:15:39
|
| Yes, do you know any workaround for this? Since that would mean i will not be able to import any other movies to XMM without deleting information. |
|
|
|
alsystems
Junior Member
USA
116 Posts |
Posted - 19 Nov 2014 : 19:05:16
|
There was a 2GB File limit in older versions Access some years ago.
However, I thought the new 64-Bit version of Access does not have this old limit but I'm not certain. I know that other competing databases such as Filemaker does not have a 2GB file limit and Access would be at a competitive disadvantage if they still had this limit.
User 'wellwet' thinks the problem is that XMM Version 8.4.2 has a bug in the 'Compact and Repair' function which deletes the MDB file.
http://www.binaryworks.it/forum/topic.asp?TOPIC_ID=13354
Anyone know for certain what the problem is?
(1) limit of 32-Bit Access
(2) limit of 64-Bit Access
(3) bug in the 'Compact and Repair' function of XMM
or perhaps
(4) Gremlins inside the computer
|
|
|
|
Mawu
Senior Member
Germany
1028 Posts |
Posted - 19 Nov 2014 : 20:34:38
|
quote:
However, I thought the new 64-Bit version of Access does not have this old limit but I'm not certain.
No the 64-Bit version of Access still has this 2 GB limit. Fore more Alessio has to implement another database engine, e.g. SQL Server Express. I would not expect, that this will happen. |
www.schlemmerkino.de - Die Nr.1 für filmische Leckereien |
|
|
|
alsystems
Junior Member
USA
116 Posts |
Posted - 20 Nov 2014 : 06:24:18
|
quote:
No the 64-Bit version of Access still has this 2 GB limit.
Wow! I thought MS fixed this this limit years ago but I guess I was wrong.
I really expected someone to claim the the problem was instead caused by gremlins, especially if you feed them data. |
|
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 03 Feb 2015 : 10:54:22
|
Hi
Any update or workaround about this issue? So far it seems last version is stable but still cannot update records cause of mdb file growt over 2GB problem.
Thanks/Best
Ari |
|
|
|
JDommi
Administrator
Germany
4657 Posts |
Posted - 03 Feb 2015 : 12:01:26
|
Doesn't seem so as if Ale has found a solution for compacting the database under the 64-bit driver.
Best would be to use Access itself for it. Maybe there is existing any 3rd party product that don't need Office installed? |
In order to achieve what is possible, you have to try the impossible over and over again.
Hermann Hesse |
|
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 05 Feb 2015 : 21:25:02
|
| I don't think compacting is the solution since i have at least 1000 movies more to update, maybe using 2 files, 1 for actors 1 for movies. Any thoughts? |
|
|
|
DrunkBell
New Member
Australia
74 Posts |
Posted - 05 Feb 2015 : 21:27:36
|
| SQL would be the best. |
|
|
|
JDommi
Administrator
Germany
4657 Posts |
Posted - 05 Feb 2015 : 21:40:53
|
Well, I have a database with only about 1300 movies and up to 12 actors per movie and that's about 250 MB. Separated I have a database with about 120 TVShows with a size of 60 MB. Both uncompacted. So if you don't import every single person related to your movies the db doesn't increase to more than 1 GB. Beside that if you really wanna see all the actors I would recommend to import a specific amount of actors with full info and in a second importing step to add further people that are not so "important" to the movie with only their names. Or just open the link in internet to see them.
I think I can say shortly: I wanna know the important things of a movie and don't wanna make a rivalry to IMDB with my database  |
In order to achieve what is possible, you have to try the impossible over and over again.
Hermann Hesse |
|
|
|
alsystems
Junior Member
USA
116 Posts |
Posted - 06 Feb 2015 : 05:08:37
|
quote:
Originally posted by DrunkBell
I don't think compacting is the solution since i have at least 1000 movies more to update, maybe using 2 files, 1 for actors 1 for movies. Any thoughts?
I don't believe you can separate the movie and actor tables in an EMM database without breaking the relational connections.
You should be able to separate the movie database into 2 or 3 separate databases either by title, year, genre. I would choose genre myself as the most logical way to separate an EMM database. You would end up with a certain amount duplication of actors but it should work. I personally specify a rather generous 20 actors per movie. Try to keep the size of the MDB file down as much as possible.
My database is 822MB and contains 3080 movies, 52000 actors. You would have to erase and re-add the actor table for each separate database since EMM currently does not have a function to remove unconnected actors. Otherwise you would be wasting a lot of space of your MDB file which is apparently limited to 2GB in the 64-bit version of EMM and approximately 1GB in the 32-bit version. |
Edited by - alsystems on 06 Feb 2015 05:13:43 |
|
|
|
Topic |
|
|
SYSTEM OUT OF MEMORY EXCEPTION II