Hi Roger
Many/most tools developed for the older 32-bit version of MapInfo Pro will also run on the new 64-bit MapInfo Pro.
If your tools are “plain” MapBasic tools, you will probably not have any issues.
There may be a few caveats though.
When we switched to 64-bit we made some changes and removed support of a few features.
Fully Qualified Paths
When creating new tables or files through MapBasic code, you need to specify a fully qualified file path.
We no longer allow you to create a table in the current directory by leaving out the path of the tab file.
Layout
The classic Layout window was replaced by the new interactive Layout Designer window.
This works in some areas differently to the old layout.
Graphs
We removed the graphs in MapInfo Pro 64-bit.
They are no longer available.
Crystal Report
We removed Crystal Report in MapInfo Pr0 64-bit.
You can no longer create reports using Crystal Report
32-bit versus 64-bit
If you have external resources or functionality in DLLs, this will only work if they have been compiled to also work on 64-bit.
Ribbon versus Menu-based Interface
We switched to the modern and context-aware ribbon interface.
We have however done a lot to make your tools load and integrate into the ribbon interface.
If your tool normally would add it’s capabilities to the Tools menu, you can now find these menu items on the Tool itself in the Tools window.
If your tool created buttonpads, the buttons from these will be created on groups on the Legacy tab.
Query Performance
As the new Layer List/Explorer Window shows a list of tables and layers, we have some cases where a tool that does a lot of queries is slower on 64-bit.
This can be fixed by closing the Explorer Window before running the tool or by using the “NoSelect Hide” keywords on Select statements and by ensuring to selecting into a name query.
I think I have covered most of the issues you may run into
You can download a trial of MapInfo Pro v2023 and give it a go.
If you run into issues, let the list here know and we can find a workaround.
Peter
From: mapi...@googlegroups.com <mapi...@googlegroups.com>
On Behalf Of Roger
Sent: 17. september 2024 19:07
To: MapInfo-L <mapi...@googlegroups.com>
Subject: [MI-L] Will MIPro 2023 run old mbx?
This message originated Externally. Use proper judgement and caution with attachments, links, or responses. |
--
--
You received this message because you are subscribed to the
Google Groups "MapInfo-L" group.To post a message to this group, send
email to mapi...@googlegroups.com
To unsubscribe from this group, go to:
http://groups.google.com/group/mapinfo-l/subscribe?hl=en
For more options, information and links to MapInfo resources (searching
archives, feature requests, to visit our Wiki, visit the Welcome page at
http://groups.google.com/group/mapinfo-l?hl=en
---
You received this message because you are subscribed to the Google Groups "MapInfo-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
mapinfo-l+...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mapinfo-l/64afe1a0-d56c-46b1-ad04-4ac1933b53ffn%40googlegroups.com.
Hi Roger
Is there by any chance anything in the Event Viewer under Windows?
I typically use the Message Window for debugging using the Print statement.
If I run in to these situations I start by adding a few Print statements like this throughout the code.
Print "A"
Print "B"
Print "C"
Print "..."
One thing I may have forgotten is that writing to the HomeDirectory$() now is an issue.
I also recommend using the temp folder.
You can get to that path using this expression:
sTempPath = PathToDirectory$(TempFileName$("")
If you are happy to share your code, post it to the forum or if you don’t want it to go public, feel to send it to me at peter....@precisely.com.
Thanks
To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/c6eef944-9240-4b30-ab25-1cce2c19e10dn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mapinfo-l/c6eef944-9240-4b30-ab25-1cce2c19e10dn%40googlegroups.com.