Greg S
Posts:63
 |
| 07/11/2008 12:34 PM |
|
|
When I try
to compile the SP4 source code I get this error in several places…
C:\Interprise
Solutions\IS2007Source\InterpriseSuiteVS2005\Interpris
e.Facade.Base\ListControlFacade.vb(395):
error BC30057: Too many arguments to 'P
ublic
Function ReadSearchResultsData(tableName As String, whereClause As String,
recordCount As Integer, viewAll As Boolean,
isEnableDataCompression As Boolean,
maxRecordsFilter As String, searchColumns() As
String) As Byte()'.
I cannot
compile the source. Please help.
Thank you Greg
|
|
|
|
|
Ramil D
Posts:218
|
| 07/11/2008 10:51 PM |
|
| Please check if the reference of the projects point to the DLL folder from the installation folder of the source code. If this problem persist even if this is configured correctly to the DLL folder try using the installation folder of Interprise Suite application instead. |
|
|
|
|
Greg S
Posts:63
|
| 07/14/2008 8:38 AM |
|
The call to the Function in the ListControlFacade.vb file is made like this with 8 parameters...
StreamData = New IO.MemoryStream(MyBase.GetBusinessServiceProxy.ReadSearchResultsData(tableName, whereClause, recordCount, viewAll, Me.EnableCompression, maxRecordsFilter, Nothing, withNoLock))
But the definition in the InterpriseSuiteBusinessServiceWse.vb file is only has 7 parameters...
Public Function ReadSearchResultsData(ByVal tableName As String, ByVal whereClause As String, ByVal recordCount As Integer, ByVal viewAll As Boolean, ByVal isEnableDataCompression As Boolean, ByVal maxRecordsFilter As String, ByVal searchColumns() As String) As Byte()
Dim results() As Object = Me.Invoke("ReadSearchResultsData", New Object() {tableName, whereClause, recordCount, viewAll, isEnableDataCompression, maxRecordsFilter, searchColumns})
Return CType(results(0),Byte())
End Function
The last parameter (withNoLock) does not appear to be supported by the function call in the webservice. If I remove the last parameter from the webservice call it compiles. But now I am getting this error...
C:\Interprise Solutions\IS2007Source\InterpriseSuiteVS2005\Interprise.Facade.Cus
tomer\BaseSalesOrderFacade.vb(1913): error BC30057: Too many arguments to 'Publi
c Sub GetSalesPriceByPricingMethod(connectionString As String, customerCode As S
tring, ByRef currencyCode As String, itemCode As String, languageCode As String,
unitMeasure As String, unitMeasureQty As Decimal, transactionDate As Date, quan
tity As Decimal, matrixGroupQuantity As Decimal, defaultPricing As Base.Interpri
seSuiteBusinessService.DefaultPricing, pricingMethod As Base.InterpriseSuiteBusi
nessService.PricingMethod, priceList As String, ByRef byTotalQty As Boolean, ByR
ef salesPrice As Decimal, ByRef isSalesPriceInBaseCurrency As Boolean, ByRef reg
ularPrice As Decimal, ByRef promotionalPrice As Decimal, ByRef pricing As String
, ByRef percent As Decimal, ByRef discount As Decimal, ByRef categoryDiscount As
Decimal, ByRef customerItemCode As String, ByRef customerItemDescription As Str
ing, ByRef inventoryItemDescription As String, ByRef basePricingCost As Decimal,
ByRef baseAverageCost As Decimal, ByRef isInventorySpecialPriceExpired As Boole
an, ByRef isCustomerSpecialPriceExpired As Boolean)'.
And again on GetOrderLineItemDefaults, DeallocateStock and GetOrderLineItemDefaults in the Interprise.Facade.Cus
tomer project. The last parameter does not seem to be supported by the Web Service call.
|
|
|
|
|
Greg S
Posts:63
|
| 07/14/2008 8:55 AM |
|
The InterpriseSuiteBusinessServiceWse.vb file seems to be the correct version (dated 5-30-08) but its definitions do not match the calls that are made to it as indicated by the errors above. As an example, the GetSalesPriceByPricingMethod definition in that file does not have the numberOfTries parameter but the call to that method is trying to pass that paramter. I think something is out of sync with the source code package.
Greg |
|
|
|
|
Ramil D
Posts:218
|
| 07/14/2008 6:17 PM |
|
| Please check the business layer if this parameter is existing on the method you mentioned. If it does then you can either add the parameter to the web services or the facade layer which ever is applicable. |
|
|
|
|
Greg S
Posts:63
|
| 07/15/2008 6:22 AM |
|
Hi Ramil,
I believe I will wait for another release. With all respect, I think this package of source code has a problem and I don't feel comfortable deploying SP4 within our company. Our guidelines for this application state that we cannot deploy a version until we have successfully received and compiled the matching source code. This is merely a mechanism to protect ourselves. After finding this inconsistency, I feel as though the released SP4 executables could not have come from this source since this source will not compile.
Do you have a timeline yet for the SP4a release?
Thank you very much for your help
Greg
|
|
|
|
|
Ramil D
Posts:218
|
| 07/15/2008 6:19 PM |
|
Hi Greg,
I apologize for these inconvenience. I am coordinating with the product division to release SP4 Hotfix 1 anytime soon. Thank you. |
|
|
|
|
Greg S
Posts:63
|
| 07/16/2008 6:23 AM |
|
Thank you for all your help and attention.
Greg |
|
|
|
|
Ramil D
Posts:218
|
| 07/16/2008 6:33 PM |
|
| Glad to be of service. |
|
|
|
|
Gary H
Posts:60
|
| 07/29/2008 8:30 PM |
|
Greg,
We dont really suggest programming in the source code unless absolutely necessary. This breaks the upgrade path. As a FYI "Post SP5" most of our internal programming will be done in the SDK.
Thanks!!
Gary |
|
|
|
|
Gary H
Posts:60
|
| 07/29/2008 8:30 PM |
|
Greg,
We dont really suggest programming in the source code unless absolutely necessary. This breaks the upgrade path. As a FYI "Post SP5" most of our internal programming will be done in the SDK.
Thanks!!
Gary |
|
|
|
|
Gary H
Posts:60
|
| 07/29/2008 8:31 PM |
|
Greg,
We dont really suggest programming in the source code unless absolutely necessary. This breaks the upgrade path. As a FYI "Post SP5" most of our internal programming will be done in the SDK.
Thanks!!
Gary |
|
|
|
|
Gary H
Posts:60
|
| 07/29/2008 8:31 PM |
|
Greg,
We dont really suggest programming in the source code unless absolutely necessary. This breaks the upgrade path. As a FYI "Post SP5" most of our internal programming will be done in the SDK.
Thanks!!
Gary |
|
|
|
|
Greg S
Posts:63
|
| 07/30/2008 7:05 AM |
|
Hi Gary,
I agree that this is not the preferred path. However let me state that this is a matter of some security for us. We are staking a large part of our business on this software and if we cannot compile the source code then we have no way to protect ourselves in the event that Interprise Solutions were to go out of business and we find a flaw with the software that prevented it's use as intended.
Since you revived this topic, let me go on to state how disheartening it is that the source code package that was distributed for SP4 could not be compiled. This would seem to be THE very most rudimentary quality control practice for this product. Furthermore it illustrates to me that the executables that were released as SP4 could not possibly have come from that source code. This is of concern to us and has been the subject of much discussion here. This too seems to need some quality control.
I am hoping and trusting that the source code pack for SP4 HF1 will be better.
Thank you for the response and for listening.
Greg
|
|
|
|
|
Gary H
Posts:60
|
| 07/31/2008 10:47 PM |
|
Hi Greg,
We are part of a multibillion dollar company with over 14,000 employees - and our sales are up more than 1000% over last year. Going out of business is very unlikely.
:)
Sincerely,
Gary |
|
|
|
|
Greg S
Posts:63
|
| 08/01/2008 7:03 AM |
|
Hi Gary,
That is very good to hear. Especially the part about your tremendous increases in sales. I am pleased to hear that information and I'm sure that Interprise Suite has many more years of growth ahead.
I still think it is a valid point of concern on our part that the source code package did not compile and I still believe that (for us) is a large enough concern that we could not deploy SP4. I am looking forward to checking out SP4 HF1 and if everything looks good, I look forward to deploying it. It has been a long, long road for us.
While I have your ear, let me mention that of the last 2 months I have sent some two dozen support requests or inquiries and have probably only gotten a response back to about 1/2 of those. It is pretty disheartening to feel like your requests disappear into a black hole. Hopefully this will improve rapidly.
Thanks again
Greg
|
|
|
|
|
Harry Y
Posts:30
|
| 08/08/2008 11:49 AM |
|
I am with Greg on this one it is BS that we paid extra for the Source Code Edition and it doesn't compile and there are a ton of errors.
FYI the SDK is full of errors and I am having a ton of compile errors with the SDK as well. It has never taken me so long to create a hello world.
So right now not only do I have SDK code that doesn't work, I have source code edition that doesn't compile properly either. Also the lack of documentation or even a starting document is not even provided.
Right now my issue is the Report Viewer. The Report only allows you to bring back one dataset because of some "so called security hole" for sql injection which is completely invalid so the report viewer can't even bring back itemized taxes. I have tried to go through the source myself but because it doesn't compile I am which doesn't help because that is the whole point of paying a premium for the source code. |
|
|
|
|
Ramil D
Posts:218
|
| 08/10/2008 7:38 PM |
|
| I would like to request that you send an email to support@interprisesolutions.com so we can do a web meeting and take a look at your system. |
|
|
|
|
Gary H
Posts:60
|
| 08/10/2008 9:03 PM |
|
Re: Source Code
The source code compiles and works in our office (we used the same source code for the builds we send out) so it might be a local environment issue. Because this requires support from one of our division leaders we are happy to do a gotomeeting, but would have to charge programming support time for this. Contact the sales department if you want to explore this option.
Re: SDK
We have a lot of partners using the SDK and we are not getting any feedback of SDK related issues. As a FYI we use the SDK internally to develop the program so if it was “broken” we would be the first to know. You may have a local environment issue that needs to be taken a look at. We strongly suggest attending a SDK training class as those who have attended the class have been far more successful using the SDK as those who did not. I cannot stress this enough.
|
|
|
|
|
Richard K
Posts:38
|
| 08/14/2008 5:01 PM |
|
I've got the SDK to compile before on my machine and it is not an easy process. Main reason is I wanted Debug DLL's for testing and development not the Release DLL's provided. The main problem with the SDK compile historically are the webservice projects which are not provided. Comment them out and you should be relatively ok. I have noticed certain changes in namespaces between releases as well.
Since not all DLL's are provided for compilation the release version does not exactly match up with the SDK Source Code. From a security perspective with much of the business logic and items stored into the Interprise.Presentation.Base libraries. If ISSI were to discontinue support then it would be difficult to continue to maintain the product.
What you should have as a customer the option to place all code into Escrow and if in the event of discontinued service or support the code is released. I do it with all of my Enterprise level customers and it is common practice.
Richard
|
|
|
|
|