After converting Macro to Module?

[samer]

After converting, shull Macro be deleted or not?

 

[DCrake]

If you do not need it then delete it

 

[namliam]

It is not deleted automaticaly.... if that is what you are asking...

 

[samer]

It is not deleted automaticaly.... if that is what you are asking...

Converting from macro to module, to run the form faster. So after converting the macro to module, do I have to delete the macro?

 

[MSAccessRookie]

Converting from macro to module, to run the form faster. So after converting the macro to module, do I have to delete the macro?

While you are not required to remove a Macro that has been converted to a VB Procedure or Function, if the Macro is not required by your Access Project for any other purpose, removing it will help you to clean up your Database a little in the process. As previously stated, the Macro will not be deleted during the conversion process, and you will need to remove it manually.

 

[boblarson]

Converting from macro to module, to run the form faster. So after converting the macro to module, do I have to delete the macro?

And you might not use so big a font.

It seems like you are shouting.

 

[samer]

While you are not required to remove a Macro that has been converted to a VB Procedure or Function, if the Macro is not required by your Access Project for any other purpose, removing it will help you to clean up your Database a little in the process.

Thanks a lot for the info.
meaning converted macro wont affect the pro performance "speed"

 

[MSAccessRookie]

Thanks a lot for the info.
meaning converted macro wont affect the pro performance "speed"

I am not sure what you mean. My experience has been that converting Macros to VB results in code that is not only faster, but also has more control over how it runs (error handling, etc.). I usually remove the old Macros because I do not like to have unused items in my databases, although leaving them in the database has no real negative side effects that I am aware of.

 

[samer]

I am not sure what you mean. My experience has been that converting Macros to VB results in code that is not only faster, but also has more control over how it runs (error handling, etc.). I usually remove the old Macros because I do not like to have unused items in my databases, although leaving them in the database has no real negative side effects that I am aware of.

thats whart i need to know, thaks again.