| T O P I C R E V I E W |
| VSUK |
Posted - 12 Oct 2014 : 13:35:32
Hi there,
I'm still having problems with this. The earlier topic pointed out that XMM x64 version seems to solve the problem, but I can't find x64 version of XMM anywhere.
Has anyone managed to get around this problem?
Many thanks,
Victor
Details about the error included below:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception (0x80004005): Not enough storage is available to process this command
at System.Drawing.BufferedGraphicsContext.CreateCompatibleDIB(IntPtr hdc, IntPtr hpal, Int32 ulWidth, Int32 ulHeight, IntPtr& ppvBits)
at System.Drawing.BufferedGraphicsContext.CreateBuffer(IntPtr src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at System.Drawing.BufferedGraphicsContext.AllocBuffer(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.AllocBufferInTempManager(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.Allocate(IntPtr targetDC, Rectangle targetRectangle)
at DevExpress.Utils.Drawing.ControlPaintHelper.ProcessWMPaint(Message& m)
at DevExpress.XtraGrid.GridControl.CheckProcessMsg(Message& m)
at DevExpress.XtraGrid.GridControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
eXtreme Movie Manager
Assembly Version: 8.3.3.0
Win32 Version: 8.3.3.0
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/eXtreme%20Movie%20Manager.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version:
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version:
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34107 built by: FX45W81RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
DevExpress.XtraEditors.v13.1
Assembly Version: 13.1.5.0
Win32 Version: 13.1.5.0
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.XtraEditors.v13.1.DLL
----------------------------------------
DevExpress.Utils.v13.1
Assembly Version: 13.1.5.0
Win32 Version:
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.Utils.v13.1.DLL
----------------------------------------
DevExpress.Data.v13.1
Assembly Version: 13.1.5.0
Win32 Version:
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.Data.v13.1.DLL
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
DevExpress.BonusSkins.v13.1
Assembly Version: 13.1.5.0
Win32 Version:
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.BonusSkins.v13.1.DLL
----------------------------------------
System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------
CustomMarshalers
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/CustomMarshalers/v4.0_4.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
DevExpress.XtraBars.v13.1
Assembly Version: 13.1.5.0
Win32 Version:
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.XtraBars.v13.1.DLL
----------------------------------------
DevExpress.XtraGrid.v13.1
Assembly Version: 13.1.5.0
Win32 Version: 13.1.5.0
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.XtraGrid.v13.1.DLL
----------------------------------------
DevExpress.XtraPrinting.v13.1
Assembly Version: 13.1.5.0
Win32 Version: 13.1.5.0
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.XtraPrinting.v13.1.DLL
----------------------------------------
DevExpress.Printing.v13.1.Core
Assembly Version: 13.1.5.0
Win32 Version: 13.1.5.0
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/DevExpress.Printing.v13.1.Core.DLL
----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version:
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
Interop.DexterLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Victor/Documents/eXtreme%20Movie%20Manager%208/Interop.DexterLib.DLL
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34004 built by: FX45W81RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
Assembly Version: 0.0.0.0
Win32 Version:
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version:
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
|
| 20 L A T E S T R E P L I E S (Newest First) |
| alsystems |
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. |
| JDommi |
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  |
| DrunkBell |
Posted - 05 Feb 2015 : 21:27:36
SQL would be the best. |
| DrunkBell |
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? |
| JDommi |
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? |
| DrunkBell |
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 |
| alsystems |
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. |
| Mawu |
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. |
| alsystems |
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
|
| DrunkBell |
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. |
| Mawu |
Posted - 19 Nov 2014 : 16:07:38
@Drunkbell
I think you reached the database limit:
https://support.office.com/en-us/article/Access-2010-specifications-1e521481-7f9a-46f7-8ed9-ea9dff1fa854 |
| DrunkBell |
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? |
| alsystems |
Posted - 14 Nov 2014 : 20:40:35
XMM 64-Bit requires the 64-Bit Access Drivers which conflict with the 32-Bit drivers of MS Office.
It appears to get XMM 64-Bit to run and still have the standard office programs you can either:
1) Upgrade to a 64-Bit version of MS Office
2) Load another office type program such as the 'Word Perfect' Suite or 'Open Office'
3) Try to get both 32-Bit & 64-Bit drivers loaded using:
http://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-install-64-bit-Microsoft-Database-Drivers-alongside-32-bit-Microsoft-Office.html
|
| Sciolto |
Posted - 14 Nov 2014 : 19:23:03
quote:
Originally posted by JDommi
Well, as said before:
System: Win7 64-bit with MS Office 2003 32-bit
Tried to install the 64-bit drivers that ends without any comment or error message
Installed XMM 64-bit succesfully
Only problem is that opening child windows like the edit window need very long to open on the first attempt
There exists a hack for installing both driver versions:
http://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-install-64-bit-Microsoft-Database-Drivers-alongside-32-bit-Microsoft-Office.html
ATTENTION:
I just have copied the link but I don't have tested this how-to !!!
Having MS Office 2007 means you won't be able to install the 64 bit drivers. The XMM 64 bit installation which is incomplete without these drivers also results in not being able to start XMM at all. Not even slowly. All of a sudden it wants me to type a password before I can access the database, which has not been password protected by me when I was using it under 32 bit.
Eventually I had to complete uninstall XMM and MS Office, very much to my disliking, and install the 64 bit drivers first before installing XMM 64 bit. This solved my problem for now, but i can't say I am a 'happy customer'. |
| Sciolto |
Posted - 14 Nov 2014 : 19:16:43
quote:
Originally posted by alsystems
quote:
Originally posted by Sciolto
The 64 bit version of XMM cannot be installed without the 64 bit MS Access redistribution SP2 pack.
This MS pack cannot be installed by people that have a 32 bit MS Office with Access, like most of us that actually have it.
If you have 32-Bit MS Office with Access and deleted Access. Can you load the 64-Bit MS Access redistribution SP2 pack without any version of Access and get XMM 64-Bit to work? I normally use Filemaker instead.
I have tried this too but it does not work. You really have to uninstall MS Office completely. |
| Madhouse |
Posted - 14 Nov 2014 : 10:56:38
Hi Alsystems,
I have 64bit Microsoft Office installed without MS Access.
I installed the MS Access redistribution pack and XMM x64 runs without problem.
It only runs a bit slower than the 32bit version in some cases.
Greetings,
Madhouse |
| alsystems |
Posted - 13 Nov 2014 : 23:45:39
quote:
Originally posted by Sciolto
The 64 bit version of XMM cannot be installed without the 64 bit MS Access redistribution SP2 pack.
This MS pack cannot be installed by people that have a 32 bit MS Office with Access, like most of us that actually have it.
If you have 32-Bit MS Office with Access and deleted Access. Can you load the 64-Bit MS Access redistribution SP2 pack without any version of Access and get XMM 64-Bit to work? I normally use Filemaker instead. |
| JDommi |
Posted - 13 Nov 2014 : 23:31:59
Well, as said before:
System: Win7 64-bit with MS Office 2003 32-bit
Tried to install the 64-bit drivers that ends without any comment or error message
Installed XMM 64-bit succesfully
Only problem is that opening child windows like the edit window need very long to open on the first attempt
There exists a hack for installing both driver versions:
http://knowledge.autodesk.com/support/autocad-civil-3d/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-install-64-bit-Microsoft-Database-Drivers-alongside-32-bit-Microsoft-Office.html
ATTENTION:
I just have copied the link but I don't have tested this how-to !!! |
| Sciolto |
Posted - 13 Nov 2014 : 22:56:07
The 64 bit version of XMM cannot be installed without the 64 bit MS Access redistribution SP2 pack.
This MS pack cannot be installed by people that have a 32 bit MS Office with Access, like most of us that actually have it.
In short: as far as I know I have to live with these irritating memory exceptions.
Alessio, I hope you are reading this. How to get rid of the exceptions if you cannot install x64 ? |
| JDommi |
Posted - 06 Nov 2014 : 21:48:42
For me it seems as if I had the 64-bit version of XMM but still using the 32-bit drivers. |
