[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::mapi_driver_for_all-in-1_office_server

Title:	MAPI Driver for ALL-IN-1 and Office Server
Notice:	See Note 6.19 for V1 SSB Kit Pointer
Moderator:	IOSG::PYE

Created:	Fri Nov 17 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	125
Total number of notes:	506

116.0. "Another drag & drop query " by CHEFS::COHEND (Took an hour to reboot the kitchen) Thu Apr 10 1997 13:05

    ALL-IN-1 IOS Server for OpenVMS V3.1 BL121 BRITISH 17-JUN-1994
    
    User reports following (not sure if NT or Win95):
    
    1. Tries to drag and drop a whole folder from  A1 to MSX. Error:
    
    An item could not be moved. Call not supported in this implementation.
    
    (NOTE: He created the blank MSX folder first)
    
    2. If he does a drag and drop of multiple files from A1 to MSX then
    this works.
    
    3. If he tries to drag and drop a folder the other way (MSX to A1) the
    error is:
    
    An ietm could not be moved. Illegal attributes supplied for Craete or
    Modify.
    
    (NOTE: The A1 folder existed but was blank - the error is the same if
    the A1 folder as an object already in it)
    
    Q. Are the above _all_ related to the fact that we are running A1 V3.1
    (not V3.1a). What about versions of Windows Messaging or NT / Win95?
    
    Customer wants to use this MAPI driver for A1 to MSX migration, so it's
    quite important that we find out what causes the above.
    
    ALl help appreciated.
    
    David Cohen

T.R Title User Personal
Name Date Lines

116.1 IOSG::MAURICE Back in the egg Fri Apr 11 1997 09:44 23

T.R	Title	User	Personal Name	Date	Lines
116.1		IOSG::MAURICE	Back in the egg	`Fri Apr 11 1997 09:44`	23
	Hi Dave, 1. Tries to drag and drop a whole folder from A1 to MSX. This won't work because we haven't written the code to support it, so the error returned is expected. 2. We have written the code to copy a document, so this is working as expected. 3. This worked OK for me. Admittedly I am using a pre-release of the next version but I don't think we changed anything here. Also the error returned is because (I think) the File Cabinet Server in V3.1 did not support one of the attributes we set. So I think you can get (3) to work if you get the customer to install the TLC (TeamLinks Connection Version) 2.5, which is not a major effort. Ideally you would get the customer to upgrade to V3.2, not for this problem, but because our next release will have V3.2 as the minimum supported version. Cheers Stuart

    Hi Dave,
    
    1. Tries to drag and drop a whole folder from  A1 to MSX. This won't
       work because we haven't written the code to support it, so the 
       error returned is expected.
    
    2. We have written the code to copy a document, so this is working as
       expected.
    
    3. This worked OK for me. Admittedly I am using a pre-release of the next
       version but I don't think we changed anything here. Also the error
       returned is because (I think) the File Cabinet Server in V3.1 did 
       not support one of the attributes we set. 
    
    So I think you can get (3) to work if you get the customer to install
    the TLC (TeamLinks Connection Version) 2.5, which is not a major
    effort. Ideally you would get the customer to upgrade to V3.2, not for
    this problem, but because our next release will have V3.2 as the
    minimum supported version.
    
    Cheers
    
    Stuart