Inserting a column of unmatched data

[CarlSeil]

Trying to figure out if it's possible to add a column of data that I don't care how to match. Basically, I need to insert some sample data into a table to replace live data for a test. So basically I have live data:

ID	Name	Amount
76543	Venkataraman	$1,200.00
76532	Mattarnovy	$720.23
76516	Simak	$1,212.13

Etcetera. And I have retrieved/generated a list of names I want to plop in there to replace:

Smith

Jones

Wilson

Peterson

So I'll basically trim the sample names to the same number of records. In the past, I think I have managed this by altering the two tables and adding an auto-increment field. Then I merge the two tables with a query that joins on the auto-increment columns. Is there a simpler way to do this without altering the tables? I obviously don't care which name goes where. I just want to end up with something that looks like:

76543	Smith	$1,200.00
76532	Jones	$720.23
76516	Wilson	$1,212.13

 

[Isaac]

This is just me, but if I were going to write a procedure to dummy-up data, I think I would write some functions that acted on character by character in a way that completely eliminated the meaningfulness of things.

For example, replace each letter with a randomized other letter of the alpha bet, rather than coming up with fixed complete values. Just one man's opinion.

 

[MajP]

This may be useful. I use this sometimes

Scramble Text

This function replaces every character with a random similar character. I use this function to anonymize data in tables. Almost but not quite entirely unlike the post made by Micron a few months ago. Share & Enjoy! Option Compare Binary Option Explicit Public Function ScrambleIt(strString...

www.access-programmers.co.uk

That was the wrong post actually. Here was the one I was thinking from @Micron

Randomizing Data for Posted db's

We often ask Original Poster to upload a copy of their db but the issue might be that it contains sensitive data. Complete data removal may not allow us to troubleshoot the OP's issue because queries, forms, etc. need records in order to observe or trouble shoot the problem. Here's a...

www.access-programmers.co.uk