G_pMapPoint->PutCaption( "MapPoint 2004 is in Automation Mode!" ) ![]() G_pMapPoint->PutWindowState( geoWindowStateNormal ) G_pMapPoint.CreateInstance( "MapPoint.Application" ) RETCODE _declspec(dllexport) xp_proc( SRV_PROC *srvproc ) MapPoint::_ApplicationPtr g_pMapPoint = NULL Your Extended Stored procedure that automates MapPoint can look like:. #Mappoint 2013 trial licenseIf you will use MapPoint only for internal purposes you won’t violate End-User License Agreement but I recommend you to contact Microsoft for more information. Take into account that standalone version of MapPoint can’t be used in the Internet environment because it has some limitations described in the End-User License Agreement. As you can see on the scheme MS SQL Server and MS MapPoint are installed on the same computer. It doesn’t matter how you invoke an Extended Stored procedure because it can be called in the same way as a regular Stored Procedure is called. Here is the picture that shows how everything works:.It means, that if you’re going to execute the same Extended Stored procedure from several client computers at the same time you have to synchronize your calls Remember, that Microsoft’s developers have created a “hidden problem” for all of us! It is related with using Extended Stored procedures in the Multi-User environment.To open SQL Server Books Online, on the Index page enter expression “ extended stored procedures” and then double click on the item debugging Believe me it will be sufficient just toįollow all steps described in the article to understand basic steps inĭebugging of an Extended Stored procedure. SQL Server Books Online has one small article and itĭescribes everything in details. #Mappoint 2013 trial how to
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |