Orchid V4, V4+ Programing Tool Support

JohnDinton

Thanks for your reply which crossed with my further post. It is indeed the modal attribute of the Show command which is not supported in Excel 97, and if I delete it the compliation errors go away. I am gradually working out how to navigate through the code, but I have not yet been able to try out my idea of disabling the Abort box as I haven't yet found the code for it.

KevinLawry

:question: This post contains code for people who know what they are doing - ask yourself if that is really you before you try it :question:

The relavent bit from the Office help file for office 2003

Note In Microsoft Office 97, if a UserForm is set to display as modeless, it causes a run-time error; Office 97 UserForms are always modal.
When a UserForm is modeless, subsequent code is executed as it's encountered. Modeless forms do not appear in the task bar and are not in the window tab order.
Note You may lose data associated with a modeless UserForm if you make a change to the UserForm project that causes it to recompile, for example, removing a code module.
When a UserForm is modal, the user must respond before using any other part of the application. No subsequent code is executed until the UserForm is hidden or unloaded. Although other forms in the application are disabled when a UserForm is displayed, other applications are not.

You could try replacing the 2 dialler sub routines with these alternatives which I think will be safe in '97 - you can drop out of the script by selecting cell A1, which you should be able to do in the dialler pause period when events are enabled.

Sub sendCarrierCodes()
    DoReset
    ThisWorkbook.Sheets("Main").Range("A3:A3").Select
    For Each carrier In ThisWorkbook.Sheets("Main").[CarrierCode]
    If ((ActiveCell.Row = 1) And (ActiveCell.Column = 1)) Then Exit For
        If (carrier <> "") Then
            Debug.Print carrier
            Application.StatusBar = carrier
            JustDial carrier
        Else
            Debug.Print "blank"
        End If
    Next
    Unload formDialCarrier
End Sub
Sub sendRoutingCodes()
    DoReset
    ThisWorkbook.Sheets("Main").Range("A3:A3").Select
    For Each Routing In ThisWorkbook.Sheets("Main").[RoutingCode]
    If ((ActiveCell.Row = 1) And (ActiveCell.Column = 1)) Then Exit For
        If (Routing <> "") Then
            Debug.Print Routing
            Application.StatusBar = Routing
            JustDial Routing
        Else
            Debug.Print "blank"
        End If
    Next
End Sub

JohnDinton

Thanks very much. Your replacement code seems to work with Excel 97. I was also able to interrupt the sending of the routing table by going to A1, although I'm not sure why I'd want to.

My next problem is how to connect the modem to the phone if you are right that it's no use going in on the line side. One possibility may be to go in through the handset connector. I am also hoping to get confirmation from Orchid of the commands for the VP3450. The instructions have commands which include the Store and Redial buttons. Clearly the CWClient server was not able to press those buttons to program it, and as there are only 12 MF4 tones it could only have sent digits 0-9, * and #. I am hoping the V4 dialler commands will also work.

KevinLawry

Not sure if I can think of a good reason to quit 1/2 way through either, but if swmbo _needs_ to make a call you might need to pause - it just replicates the abort buttons functionality.

There are of course 16 DTMF tone pairs, it is a 4x4 matrix, but given that they have a working command set using just the ones found on a common telephone I would expect them to be used in much the same way as the V4

archie159

Hi Kevin, and thanks for your reply. No luck yet, I'm afraid, and a further mystery (to me, at least). Firstly, in answer to your questions:

Does it finally finish and have the ABORT box exit returning you to the spreadsheet? Yes.

If it does, can you then select, say, cell M30, click the 'Dial Single Table Entry' button and hear the tones? No - on clicking this button, one gets a "single string..." message box, then a egg-timer for a few seconds, but no noise of dialling.

You might try changing the value of the 'Post Dial Pause' setting on the config page to something a little higher to see if it makes a difference - perhaps 5 for a start, it will make the whole process take a little longer, but if it works you can reduce it step by step until you hit the problem again. Tried that, makes no difference. Also tried switching the "Advance reset required" box between 1 and 0. Also tried fiddling with settings in modem control panel (eg removing requirement to wait for dial tone). None of these helped.

This is where it gets odd... I noticed that the dialling always stopped at line 26 (up to 25 was fine); I have 30 lines. So what I then tried doing was removing some of the earlier lines from the table for entries I reckoned I could do without (eg speaking clock), and cut-and-pasted the extra lines from below into the gaps. I then noticed when dialling the routing table that it skipped over the lines which had been moved up (ie they appeared in the abort box, but with no dialling sounds, but when the next line appeared "noisy-dialling" continued as it should). I have tried to identify anything in common for the missed lines, but cannot see anything. Some of the missed lines are yours (eg the 999 entry, which I had not touched in any way), and some are mine. I haven't delved into the code which appears in the fx line at the top, as that is way beyond my understanding. But it doesn't seem that my modem simply gives up after 25 lines - there is something in some of them which seems to be stopping it dialling, even when they are moved up to near the top of the table.

I'm not sure if this all makes sense, but I'd be most grateful if you or anyone else have any ideas for solving this!

with many thanks again - I do appreciate your help.

"Archie"

KevinLawry

I'll PM you my e-mail address, can you e-mail me a copy of your failing spreadsheet and I'll have a look to see if there is anything that I can identify as the problem

KevinLawry

I have received the spreadsheet, and listened to it dial the numbers all the way through the list several times without fail (almost true, it crashed when it was dialling a number as the time passed midnight, but I think that is a coding error - dont set up your v4 at midnight people)

Now digging way back in a failing memory, I seem to remember that some modems had weird blacklisting rules that would 'lock out' some numbers that were deemed inappropriate - such as auto-dialling 999, that kind of thing - and I wonder if we are falling foul of a bit of that in a dodgy old driver.

Can you please select cell m12, which is on your failing line 8 and holds the code to be dialled, and then click on the 'Dial Single Table Entry' button. you should get a pop up confirming the number to be dialled, OK that and see if you hear the tones - let me know the result. I am expecting silence but we shall see.

Also, if you are able, can you let mem know the make of the modem that you are using - I know it is built in, but the drivers should indicate what you have

FJSRiDER

Just downloaded the spreadsheet and am working my way thorough the set-up. Couple of questions.

1. I can't add the 9th carrier code (I need to call landlines and mobiles in Japan and UAE (Dubai)) and there are separate suppliers for all of them. Carrier code is fine up to line 9 - then it is greyed out and doesn't auto fill. Tried copying the line above but it give me a cell is 'protected and read only' error.

2. I've worked through this thread but can't find what the codes in 'Handling' mean. I've got a vague recollection of something in CWclient but have no idea what I used back then.

Heinz

The maximum number of Carrier Codes may still be 8 (it used to be 8 when CW Client was the means of programming and, although a 9th row was always visible, it was written into the instructions not to use the ninth).

Handling codes are largely self-explanatory - see columns O and P in Kevin's spreadsheet..

A(3), B(1), L(4) and T(5) are obvious but, personally, I never really understood the exact reasons for 'Special' and 'Exception' but just accepted (and copied) the way Orchid used them

FJSRiDER

Heinz wrote: »

The maximum number of Carrier Codes may still be 8 (it used to be 8 when CW Client was the means of programming and, although a 9th row was always visible, it was written into the instructions not to use the ninth).

OK. I'll work round that by using 18185 for Dubai land line calls.

I'm presuming that if I leave 19 '00 International prefix...' and simply add the other specific Japan and UAE numbers that it will not use '00xx...' number and the specific ones instead (if you see what I mean?)

Heinz wrote: »

Handling codes are largely self-explanatory - see columns O and P in Kevin's spreadsheet..

A(3), B(1), L(4) and T(5) are obvious but, personally, I never really understood the exact reasons for 'Special' and 'Exception' but just accepted (and copied) the way Orchid used them

I missed that bit off the side of my screen! :rolleyes: Makes sense and is as I remember it now. Mostly I'll be adding 'A'.