Jeff Overcash

IBX determines whether to create an ISQLVar_1 or ISQLVAR_2 based on the return from isc_get_client_version from the client library. >= 7 is V2, otherwise V1. Sounds like you are either using the IBClient DLL or the FB people are now returning >= 7 for that function call in their client DLL (I suspect the former moreso than the later). If FB does not support SQLDA_V2 (sounds like from the error message) you need to use a client library that returns 6 or less from the isc_get_client_version. If you want to check what the library you are loading returns call Database.GDSLibrary.GetIBClientVersion where Database is an IBDatabase. If that is >= 7 you are going to get SQLDA and SQLVar that are V2. The easiest solution is probably to make sure you are using the correct client library. Another solution is to create your own FbClient Library and your function for GetIBClientLibrary should return 6 and not call into the client DLL at all. You can do this 1 of 2 ways. First would be to fully copy the TIBServerLibrary class from IBX.IBInt.pas into it's own file. Change its class name. Modify the GetIBClientLibrary function to return 6. In the initialization section of that new file registry your client library with the IBX library system. initialization FbServerLibrary := TFbServerLibrary.Create; AddIBInterface('FbServer', FbServerLibrary); {do not localize} finalization FbServerLibrary := nil; end. A simpler, but similar method would be to take IBX.IBIntf.pas and modify the TIBServerLibrary to set GetIBClientLibrary to virtual. Again create your own TFbServerLibrry that inherits from TIBServerLibrary and override GetIBClientLibrary to return 6. Again do the registration it above. and add both your and the modified IBX.IBIntf.pas to your project. Your Database's ServerLibrary would be FbServer instead of IbServer. If you put your new interface into a design time library and install it into the IDE you will see it listed as available library files to be used at design time. If doing this I would also override the function LibraryName: String; and return the name of the Fb client (FbClient.dll or whatever it is for 32 and 64 bits); The there is no mistaking accidentally grabbing the IB dll when you wanted the Fb one (in the past they shipped their naming and the IB naming which could cause the wrong library to be loaded if both are available on the machine). Next Interface breaking release I'll make that function virtual in the shipping version. I really think it is more likely you are picking up an IB client library when loading instead of the Fb client. I rather doubt they are returning 7+ from isc_get_client_version. Placing a copy of the Fb client in the same directory as the exe should resolve that. Please note, IBX does not support nor tested against Fb. As long as they stay backwards compatible you should be fine, but if they don't I won't make changes to IBX to support their backward compatibility-breaking changes.

Clear not only the Fields property but the FieldDefs too. Do this while the dataset is closed. Then you can rebuild your new fielddefs. if FDMemTable1.Active then begin FDMemTable1.Close; FDMemTable1.Fields.Clear; FDMemTable1.FieldDefs.Clear; end; Now it is ready for you to define the new columns. Index etc done the same way, just clear their definitions. Don't forget there are both an Indexes and an IndexDef, both should be cleared. Filter you would just assign the empty string.

Database unavailable often happens because you have multiple InterBase installs and have the IB_PROTOCOL environment setting set either globally or within the IDE's local variables. If that variable is set it must match the running server's port name. If it doesn't you can not make local connections only loopback TCP connections. You do not need IB_PROTOCOL set for anything it is just a quick way to identify the running instance so you can remove the environment variable without worry. It is one of the first things I remove after installing a new RAD or new IB instance (I keep all mine on port 3050 just manually start the one I want to test against).

A little more on this. There was originally a bug with deletes so you need the latest patched version of IB (2020 and 2017 I am sure). But with FireDAC there is more you have to do to see deletes. "FireDAC is very different. In order to display deleted rows from a ChangeView, it is necessary to switch the FDQuery into cached updates mode. You then have to add rtDeleted to the FilterChanges property, which is only available when CachedUpdates is true. Once I did this, I saw the deleted rows. So it would seem, with a default FDQuery, deleted rows are actively excluded when querying from a change view that records deleted rows"

I am not familiar with how FireDAC ended up implementing it. IBX has an IBSubscription class for managing subscriptions, but much beyond that it will be manual to transfer changes from the main DB to a secondary or back. You would just start a snapshot transaction, turn on the subscription read the data like normal and then walk the result set to and use a second connection and component to apply the changes. Adding some sort of merge feature would not be that difficult I think, but also something I'd have to wait until the next time I can do an interface breaking change. Probably as simple as a MergeChangesTo and you pass an IBDatabase to use and it would use the existing InsertSQL et al but against the passed connection vs the original one.

I do recall an issue with FireDAC and Deletes in Change views (for some reason IBX was not affected). I thought it was fixed in the latest patches for both 2017 and 2020, but I might be mistaken on that. I have pinged Sriram on this to see if he can shed more light on it.

That would be a bug in FireDAC. What you can do though is in your DB set up an Int64 domain that is numeric(18,0) and then it should go through. I had a similar bug in IBExtract in IBX.

Try numeric(18,0). InterBase does not have an alias for Int64 directly, but 18,0 is an int 64.

While I do not support Firebird, I also try not to introduce incompatibilities. As long as Fb does not break backward compatibility you should be ok. There is one caveat with this and it is more around the service API I think. In most cases the Fb developers made sure to introduce new constants in a range higher than the original 6.0 open source release so they would not overlap with new ones introduced by IB. With the service API though they just started at the next number so there are instances that Fb constant reflects a different function than the IB one. For the past 22 years though there have been very few incompatibilities. One of the reasons I went to an Interface/registration type system (see IBX.IBIntf.pas) for loading and resolving the client interface was so the Fb users could easily create a FbServer (which would look much like IBServer) class and intercept when data needs massaging to Fb constants before being sent to the server. Some new features may or may not work like the RAD 11.0 PrecommittedReads feature to do reads through a connection-level pre-committed transaction so the dataset can stay open forever without causing OIT/OAT issues. I do not know if Fb ever copied that feature from IB.

InterBase does not return a record count on a select statement (it always returns 42) because this is expensive to do. So RecordCount reflects the number of records fetched to the client. Just call FetchAll after open if you want an accurate RecordCount. If you are going to loop through the records just loop till Eof. RecordCount is not needed to work through the result set. FindFirst and FindNext are when you are filtering a Dataset on the client side.

To get the count of days in a month just subtract (as dates) the first day of the next month from the first day of this month. Actually, as long as the day is the same from both months that works too so don't have to start with day 1 of the month. select cast('2/1/2021' as date) - cast('1/1/2021' as date) from rdb$database returns 31. select cast('3/15/2020' as date) - cast('2/15/2020' as date) from rdb$database returns 29 for Feb in 20202 etc. Stano's only gives you the dates of the first and last days of the passed in month, you still need to subtract them and add 1 to get the number of days.

your problem is in your empty Table procedure TfrmEntry.EmptyTable(tbl: TADOTable; tablename: string); var MyCmd: TADOCommand; begin tbl.Active := true; MyCmd.CommandText := 'Delete * from '+tablename; MyCmd.Execute; tbl.Active := false; end; You have a local variable named MyCmd, but you never initialize it. Nor do you hook it up to the connection. try this instead procedure TfrmEntry.EmptyTable(tbl: TADOTable); var MyCmd: TADOCommand; begin MyCmd := TADOCommand.Create(nil); try MyCmd.Connection := tbl.Connection; MyCmd.CommandText := 'Delete * from ' + tbl.TableName; MyCmd.Execute; finally MyCmd.Free; end; end; Note you have 2 MyCmd variables. One is local to your EmptyTable procedure and one public to your form, but neither is shown to ever be created. You need to both instantiate a TADOCommand object (the .Create ) and you need to tell it what connection to use (setting the connection property). Don't forget to clean up the variable when done.

Actually, the message is accurate. You do not have a table alias visible in the set part named I. Assuming Currate is in the invoice table (what you aliased as I "I" the where clause tryt UPDATE INVDETAIL ID SET ID.UPRICELOCAL=(ID.UPRICE-(ID.UPRICE * ID.DISCPERC /100)) * (select I.CURRRATE from invoice i where i.rno = id.rno) WHERE EXISTS (SELECT 1 FROM INVOICE I2 where I2.RNO = ID.RNO) This part (select I.CURRRATE from invoice i where i.rno = id.rno) should reflect wherever currrate is.

IBDatabase works just fine. You set the Server type to IBEmbedded instead of IBServer to work with the embedded version of IB (Either IBToGo or IBLiite, license determines which mode the embedded works as).

Because Precommitted transactions do not get a transaction ID and can basically run forever without causing growth in the TIP page, the wisql window in IBConsole defaults to read-only transactions (not to be confused with a read-only database). To change this click Transactions | Options and just switch the radio button from read to write. If you always want it to be a writeable transaction check the Set as Default at the bottom.