Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
BowDown
Starting Member
1 Post |
Posted - 2008-06-24 : 08:50:07
|
| Here's my issue...Our design software (Alpine) used to have an Access MDB database it used for keeping track of sales orders. Now they have transitioned to a SQL Server 2005 stored database. I don't have any problem combining the 13 tables of crap together to get what I used to get from 2 tables.. but the issue I have is that Alpine says that they change their database scheme often with new software releases. I can't have this.My accounting software has been customized with import features that will go out to my design software database (Alpine) and pull in all sales order items and order Head details and created an automated order. I can't have the field names changing constantly. It would result in many expensive changes to the accounting software...So what I'm thinking is I will create my own database in SQL, then somehow write an import routine that will go out to the Alpine SQL database, query/format/insert the information into my SQL database. Then have the accounting software linked to query my database tables. I have written the queries already in VB.. and I know my table structure works.. but how can I impregnate this VB code into my SQL database structure so the accounting software can just make a function call that will populate my database based on a JobKey value, then query my database for the results...?Thanks! |
|
|
|
|
|