×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi everyone
Before I forget - we are on V7r3
Are we all sitting comfortably - then let me begin
We presently hold tokens instead of credit card numbers and the web service calls that are made for settling, authorization, refunds etc. use the token
The token was of a length that we could store it in the old credit card number field - 17 characters
However - we have been informed that the size of the token is going to increase - to larger than 17 characters
I understand that there will be NUMEROUS service programs, files, programs etc, that will need to be changed and tested
Here is my question -
Opinion based or fact based - What would be better -
1. expanding the present field from 17 to a much larger field (say 50 - just in case of future increases)
2. Adding a new field (at the end of all the files)
Each has their own foibles (for want of a better word)
For example:-
Option 1 - EVERY program that even touches any of the files that this type of file change is applied to will need to be re-compiled (minimum) - even if the program has nothing directly to do with this expanded field. However it will be the same field name, therefore only need to be concerned about the new field size and what is happening to that field (populating another field for example)
Option 2 - EVERY program, service program etc. will need to be changed to use the new field name. Not only need to be concerned about replacing the old field name with the new field name within the program, service program etc. but also need to be concerned about the new field size and what is happening to that field (populating another field for example)
If anyone has more options - please feel free to pass those on
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.