Pin number code issue, 2

[enigmatic1]

Hello,
I am writing an access script that takes account information from one DB and uses a portion to create PIN numbers.
There are 2 seperate sides to this DB as well. I am also attempting to have it verify the users from one and when duplicates are there use the same PINs for both.
Although I have a portion of the script done it seems slightly buggie and I was hoping to maybe get some input on where mine is wrong.

Thanks in advance,

 

[PHV]

it should generate the same PINs for the same SSN
So, use a formula that don't invoke random values nor actual timestamp !

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[enigmatic1]

We tried to get approval for non random values, our Corp HQ denied that one all together.
We were given certain standards for the codes that must be met. So I am only working with what was thrown at me.

 

[fneily]

That is why I suggested generating the PIN once for a SSN. Then store that in a table with the appropriate SSN or SSNS. I'm actually surprised that you ever get duplicate PIN's with the same SSN because of the random generator. The purpose of RND is same data in, DIFFERENT data out.
"Also the issue is we cannot create other tables due to the fact we are using 3rd party". The 3rd party stuff is left untouched. You can create your own table. You are the developer.

 

[enigmatic1]

No we have an agreement regarding the structure, we had to have them create the table although we wanted to.
The reason being is they do random updates to their SW and they hold no responsibility to our DB becoming unstable if we change anything.
WEhave been given VERY limited editable areas within their program. I will talk with them however and see what they will agree on.

 

[enigmatic1]

fneily,
speaking on the script as it is isnt there a way to take the RND number in and have it check for the same SSN and then spit out the same pin when the SSN is the same?

 

[fneily]

Reverse engineer the RND and your formula. Interesting. I'm sure NSA could do it, but I have no software to do it. If you could, you wouldn't need to send the SSN through the process again, you all ready have the output. Of course, if it can be done, then it's a sad security technique.
Has it occurred to you that since you are so restricted from doing anything to the database, give your request to THEM.
Can't you just match Lender's SSNs to Loan's SSNs and then assign whatever PIN popped out the first time?
Sure is an enigmatic one. Get it? enigmatic1.

 

[enigmatic1]

hahahhaa,
Yah I was pondering this last night, and I believe the same thing. I need to create the script that hits both Lenders and Loans together at the same time. Does a search and then matches them against each other. I believe the copy function is a relentless nightmare to no where. However the 3rd party company has told us they will not modify their code to this degree. Actually what their SW Engineer told me was "I do not want to talk about it". That was prior to hanging up, LOL.
And this project was thrown into my hands after my predecessor left. So I am working to make something from total confusion which I new it was before hand.
So fneily lets say for the sake of argument with their SW guys I decided ok lets look at another way of doing this. Can you give me any modification suggestions you might have. I am thinking about just saying to H*** with it and making the modifications on a backup copy then exporting the live data on a daily feedback to it.

Yes and this one is an Enigma, LOL

Thanks again,

 

[fneily]

Actually, that's not a bad idea. Very good. Since the developers are being dolts, make a copy of the database and do your thing in that one. Then, as you said, export/import the necessary results back. No one need to know.
I've given you my suggestions - create a PIN function, create a PIN table connecting to the SSN's.

 

[enigmatic1]

fneily,
This is where I may need a little more help. My degree of skill with Access building is limited although yes most of what is here I currently handled. Could you please give me some layman logic on how I should build this. Or tell me if what I am saying here is correct.
Basically take the Table PINs and connect it to both the SSNs in Lenders and Loans. Have it process both tables simultaneously, then have it spit out the results into a new Tables lets say PPINs. Instead of running this back and forther create and copy commands which are not obviously going to function as needed.
Now the question becomes once I have the tables built how do I have it run the verify command on the Tables for duplicate SSNs.
I think I get what your saying however it is still a little Hazy...