Messaging Plugin

Hi:

We are in the processing of migrating from V1 to V3.04 and V2 to V3.04
Everyting goes well. Except of course they are always some minor
issues.

Server running in Win7.
Clients in XP


1. We have the following error with in GetMessagingClients in Messaging
Plugin:
EreaderError with messages 'Invalid Property'.

2. The following code works in V1:
InvoiceData.Filtered := False;
InvoiceData.SetRange([PatientObject.AcctType._Account],
[PatientObject.AcctType._Account]);
InvoiceData.Filter := 'PatientNumber = ' +
inttostr(PatientObject.AcctType._PatientNumber) + ' and ' +
' InvoiceType = ' + cSep + '1' + cSep;
InvoiceData.Filtered := true;
InvoiceData.blockreadSize := ciReadBlockSize;

It wil generate an error in V3. I think blockreadsize creates ther
problem in this particular sequence.

Thanks



Ken


--
Kenneth

> 1. We have the following error with in GetMessagingClients in
> Messaging Plugin:
> EreaderError with messages 'Invalid Property'.

You are using the plugin source that comes with v3, right? Exactly
when/under what condition do you see the error message?

> 2. The following code works in V1:
> InvoiceData.Filtered := False;
> InvoiceData.SetRange([PatientObject.AcctType._Account],
> [PatientObject.AcctType._Account]);
> InvoiceData.Filter := 'PatientNumber = ' +
> inttostr(PatientObject.AcctType._PatientNumber) + ' and ' +
> ' InvoiceType = ' + cSep + '1' + cSep;
> InvoiceData.Filtered := true;
> InvoiceData.blockreadSize := ciReadBlockSize;
>
> It wil generate an error in V3. I think blockreadsize creates ther
> problem in this particular sequence.

"An error"? Please be specific. I can't offhand see anything wrong with
the above.

--
Eivind Bakkestuen [NDD]
Nexus Database Systems

Eivind, sorry for the confusion:


1: When we execute the following , we get the error.

Procedure TOS2RemoteMessageObject.getClients;
Var
AList: TpsnxRegisteredClientList;
Index, i, j: Integer;
ok: Boolean;

Begin
If Not gDBVarsPathObject.bServerAvailable Then
Exit;
AList := TpsnxRegisteredClientList.Create;
ok := true;
Try
Try
kbmMemTableMsgUser.emptytable;
Try
OS2RemoteMessagingPlugin.GetMessagingClients(AList ); <---
'Invalid property value'.
Except
ok := False;
End;

2: Operation not allowed on a unidirectional dataset occurs where
executing the following

with tbAppt do
begin
SetRange([_AcctType._PatientNumber], [_AcctType._PatientNumber]);
Filter := 'OriginalStatus = ' + cSep + 'R' + cSep;
Filtered := true;
blockreadSize := ciReadBlockSize; <--- cause error in V3
while tbAppt.EOF = False do
begin
if (FieldByName('AppointDate').asDateTime >= Date) and
(FieldByName('TimeSlot').asInteger > curTime) then
begin
cRecallType := 'B';
rdate := FieldByName('AppointDate').asDateTime;
Exit;
end;
tbAppt.Next;
end;
end;


Thanks


kenneth


--
Kenneth

> 2: Operation not allowed on a unidirectional dataset occurs where
> executing the following

It sounds as though you have a grid hooked up. A grid can't be hooked
to a unidirectional dataset (which is what you get with BlockReadSize).


--
Eivind Bakkestuen [NDD]
Nexus Database Systems

> OS2RemoteMessagingPlugin.GetMessagingClients(AList ); <---
> 'Invalid property value'.

Have you tried the example program that comes with the messaging
plugin? I just did, and I did not get any errors (made up a custom
server, using D2010). The function returned with the expected results.


--
Eivind Bakkestuen [NDD]
Nexus Database Systems

Eivind:

I just resinstall Win7 and D2010 in my computer,in case something
corrupted.

Install remotemessaging in the server according to instruction.

Execute demo program in the bonus dir.

If you hit the 'Get Clients' button, you will get the following message
'Invalid property value' , at least is in my system.


--
Kenneth

> If you hit the 'Get Clients' button, you will get the following
> message 'Invalid property value' , at least is in my system.

Make sure the NX_EXCEPTION_LOG define is on, and show me whats logged
in nxServerException.log. If nothing is logged there for this error,
please show the exception stack copied from Delphi when it stops in the
debugger. As I said, I couldnt reproduce here.

--
Eivind Bakkestuen [NDD]
Nexus Database Systems

Eivind:

I recompiled nxServer 3 With D7 and everything works perfectly. I Have
no idea what cause the issue in our office and why it works in your
computer, btw there are no error in the server.

I read the other message and I think they have the same problem as mine.


Anyway, we are in a hurry to migrate to NX3 and I will stick this
particular fix for the time being.

Thanks for your help.


Kenneth


--
Kenneth