macro

[doriano]

to all
I used to work with s.e. v20 and I had a lot of macros for the tables that speeded up my work a lot.
Now I bought a new notebook where I work with st5.
my question is if I can copy these macros to the key and bring them to the notebook.
What is the procedure?
Thank you.
p.s. you would solve me a good problem

 

[Tequila]

the macros you had on the v20 you will have installed them and then recalled by the cad by adding the command icon, or only "fishing" the link to the executable from solid edge.
on the st5 do the same thing, install the macros on the laptop, or cover the executable from pc to notebook.
from open st5 go on customization, quick access, choose macro and look for the path where the macro is located and add it to the horizontal bar

 

[doriano]

Yes, on the v20 I had macro icons. I will try to do as you told me in the hope of succeeding.
Thank you.

 

[doriano]

thanks for your advice I managed to put all the macros and only work some no and when the active give me this message.

information about how to call debug jit (just-in-time) instead of this window
are reported at the bottom of the message.

[Bleep] [Bleep] [Bleep] [Bleep]
system.runtime. interopservices.comexception (0x80020005): incompatibility between types. (except for hresult: 0x80020005 (disp_e_typemismatch))
in microsoft.visualbasic.compilerservices.latebinding.lateget(object or, type objtype, string name, object[] args, string[] paramnames, boolean[] copyback)
in microsoft.visualbasic.compilerservices.newlatebinding.lateget(object instance, type type, string membername, object[] arguments, string[] argumentnames, type[] typearguments, boolean[] copyback)
in inserisci_rugosità.inserisci_rugosità.ins_rugosità(object file)
in system.windows.forms.control.onclick(eventargs e)
in system.windows.forms.button.onmouseup(mouseeventargs mevent)
in system.windows.forms.control.wmmouseup(message& m, mousebuttons button, int32 clicks)
in system.windows.forms.control.wndproc(message& m)
in system.windows.forms.buttonbase.wndproc(message& m)
in system.windows.forms.button.wndproc(message& m)
in system.windows.forms.control.controlnativewindow.wndproc(message& m)
in system.windows.forms.nativewindow.callback(intptr hwnd, int32 msg, intptr wparam, intptr lparam)


************** assembly caricati **************
mscorlib
versione assembly: 2.0.0.0
versione win32: 2.0.50727.5466 (win7sp1gdr.050727-5400)
base di codice: file:///c:/windows/microsoft.net/framework64/v2.0.50727/mscorlib.dll
----------------------------------------
inserisci_rugosità
versione assembly: 1.0.0.0
versione win32: 1.0.0.0
base di codice: file:///c:/program%20files%20(x86)/solid%20edge%20v20/custom/macro_bmv/inserisci_rugosit%e0.exe
----------------------------------------
microsoft.visualbasic
versione assembly: 8.0.0.0
versione win32: 8.0.50727.5420 (win7sp1.050727-5400)
base di codice: file:///c:/windows/assembly/gac_msil/microsoft.visualbasic/8.0.0.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
----------------------------------------
system
versione assembly: 2.0.0.0
versione win32: 2.0.50727.5467 (win7sp1gdr.050727-5400)
base di codice: file:///c:/windows/assembly/gac_msil/system/2.0.0.0__b77a5c561934e089/system.dll
----------------------------------------
system.windows.forms
versione assembly: 2.0.0.0
versione win32: 2.0.50727.5468 (win7sp1gdr.050727-5400)
base di codice: file:///c:/windows/assembly/gac_msil/system.windows.forms/2.0.0.0__b77a5c561934e089/system.windows.forms.dll
----------------------------------------
system.drawing
versione assembly: 2.0.0.0
versione win32: 2.0.50727.5467 (win7sp1gdr.050727-5400)
base di codice: file:///c:/windows/assembly/gac_msil/system.drawing/2.0.0.0__b03f5f7f11d50a3a/system.drawing.dll
----------------------------------------
system.runtime.remoting
versione assembly: 2.0.0.0
versione win32: 2.0.50727.5420 (win7sp1.050727-5400)
base di codice: file:///c:/windows/assembly/gac_msil/system.runtime.remoting/2.0.0.0__b77a5c561934e089/system.runtime.remoting.dll
----------------------------------------
mscorlib.resources
versione assembly: 2.0.0.0
versione win32: 2.0.50727.5466 (win7sp1gdr.050727-5400)
base di codice: file:///c:/windows/microsoft.net/framework64/v2.0.50727/mscorlib.dll
----------------------------------------
system.windows.forms.resources
versione assembly: 2.0.0.0
versione win32: 2.0.50727.5420 (win7sp1.050727-5400)
base di codice: file:///c:/windows/assembly/gac_msil/system.windows.forms.resources/2.0.0.0_it_b77a5c561934e089/system.windows.forms.resources.dll
----------------------------------------

************** debug jit **************
per attivare il debug jit, è necessario impostare il valore
jitdebugging nella sezione system.windows.forms del file di configurazione
dell'applicazione o del computer (machine.config).
l'applicazione inoltre deve essere compilata con il debug
attivato.

ad esempio:

<configuration>
<system.windows.forms jitdebugging="true"></system.windows.forms>
</configuration>

quando il debug jit è attivato, tutte le eccezioni non gestite
vengono inviate al debugger jit registrato nel computer,
anziché essere gestite da questa finestra di dialogo.

 

[Be_on_edge]

I think it's a problem of libraries or ocx... You should ask who wrote the macro.

Hi.

 

[delki]

Are you using a 64-bit machine? because it seems like you turn a 32-bit macro on 64-bit systems. vb6 cannot fill in 64 bits, and when looking for 32 dlls, which in 64 are not there, macros do not work.

 

[doriano]

Are you using a 64-bit machine? because it seems like you turn a 32-bit macro on 64-bit systems. vb6 cannot fill in 64 bits, and when looking for 32 dlls, which in 64 are not there, macros do not work.

I think you're right because these macros were made on 32bit pcs and now I want to insert them on 64bit pcs.
you know if you can change to make them compatible with 64bit.
However a part of these macros work others partly work for nothing.
Thank you.

 

[Be_on_edge]

I think you're right because these macros were made on 32bit pcs and now I want to insert them on 64bit pcs.
you know if you can change to make them compatible with 64bit.
However a part of these macros work others partly work for nothing.
Thank you.

vb6 can only fill in 32 bits so if necessary macros should be rewritten in .net and compiled to 64 bits.

I think it's just a problem of having the right 32-bit dll registered in the system.
all my macros written on xp 32 bits now on win 7 to 64 bits continue to work.
on a couple of pcs I had to copy some dlls (and record them) in the system32 folder to make them work.

Hi.

 

[delki]

vb6 can only fill in 32 bits so if necessary macros should be rewritten in .net and compiled to 64 bits.

I think it's just a problem of having the right 32-bit dll registered in the system.
all my macros written on xp 32 bits now on win 7 to 64 bits continue to work.
on a couple of pcs I had to copy some dlls (and record them) in the system32 folder to make them work.

Hi.

the problem is if the call is on the system dll already present and recorded to 64 bit.