For example several DLLs belong together and they should all be in same folder, so Windows can find them. You passed an invalid path to the DLL or you tried to load a DLL and it refers to another DLL, which could not be found. Windows DLL Loading errors When you try to load a DLL on Windows via our plugins, you may get back an error message on failure.Įrror 126: The specified module could not be found.
#Xojo program arguments pdf
Once you remove the Adobe PDF Viewer plugin, the default PDF viewer will kick in and show PDFs. Xojo) and embedded webkit controls before. We've see such crashes with other development tools (e.g. $r = MBS(" Files.MoveToTrash" "/Library/Internet Plug-Ins/ugin")
Some clients even automate this by putting a line like this in the start script: Your users probably won't miss it and your FileMaker solution is more stable. We recommend to remove it and avoid those crashes. And the Adobe control is optimized to run within a browser and not the FileMaker application. But Safari and other browsers have such a viewer built-in, so the Adobe one is not needed. Adobe PDFViewer crashes in FileMaker If you see crashes in FileMaker related to showing a PDF document inside an interactive container field, you may want to take a closer look.Ĭlick details on the crash report and look which thread crashed.
0 kommentar(er)
