Software

Ask something
Discussion Locked

Access Merge one Record at a time.

0 helpful
5 replies

by mjervis 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Access 97 Format only.

Ok here's the deal. We already have an Access database designed. We would like to build an addon for this database. To give an example lets say we have a current database of customers and orders that have been filled. I would like to keep the integrity of this database but I would also like to ease the use of our "salespeople" by automating thier order taking process.

Therefore I would like to build a seperate module that will take orders, from there I would like the orders to go into one file not into the main database.

From there I would like the "order processor" to be able to use one record at a time and import that record into the main database after they add their information to the records.

Thus taking the records one record at a time out of the first database and importing it one record at a time into the main database.

I know the theory of how I want it to work. It the mechanics I am not sure of.

Any help would be appreciated.

Thanks in advance.

5 replies

by is

This may be what you are looking for. What you want to do is add a button to your form. Attach it to a macro or code that will run your query to move the record. Set a unique field (autonumber works great) on your form and add the reference to the field on your current form as the criteria. This will allow you to move only the record currently being viewed.

by roc180

Your question is really one of architectural layout. Are your salespeople local or global, how do they connect to the "Main" DB, is your "Main" DB networked? To really give you a good answer I need to understand the constraints, both hardware and user of your system. From a very rudimentary perspective you can build multiple mdbs to handle the different functions of your process (Order taking, Order processing, etc). You then need a middleware component to do work, basically move data around and apply business rules. This is where things are tricky in Access, your middleware will more than likely have to be initiated by human intervention (Button clicking). If you have many sales people (30+) I would considered re-architecting the app using SQL Server, you can then take advantage of scheduled events and automate the system to a higher degree.

That's my 2 cents, if you would like to discuss further feel free to Email me.

Good Luck
Neal Martinelli

by mjervis

I understand it would need intervention, in fact I don't want the records moved without intervention. In a day of automation there are still things that need to be left to humans.

This discussion is closed to new replies.