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 |
|
TRIMS30
Starting Member
1 Post |
 Posted - 2014-11-30 : 16:29:39
|
| Have been assigned the job of converting a VB6 application to VB.Net and SQL database. Old database was a non-sql record manager - very fast but 1996 vintage.I'm OK with the VB.Net coding as well as basic SQL but there are many questions I have regarding most efficient procedures for accessing and displaying SQL data.Let me describe how old system works and I'd appreciate comments on how this should be done in an SQL Server environment.Something basic - Inventory - 15,000 items Old system displays records on a grid - not all fields - just Stock No, Description, Price and Qty.Grid can be searched using scroll bar or by entering all or part of a Stock No or description Key and clicking search button.Once item is found, grid is positioned to that item and it is possible to scroll grid forward or backward from that point using current Key sequence. An inventory item can be edited by selecting it from the grid and clicking the Edit button. An edit screen opens with all data fields exposed for editing. Saving the edit causes the grid to reappear and display current info for that edited item.Clicking an Add button on the Grid causes the Edit screen to appear with no fields populated. Operator enters data and saves it. Saving causes the grid to reappear and be positioned to display that new item.Deletes from the grid cause selected item to be deleted and grid positioned on next item in table.Since we're not doing edits on a row in the displayed grid (as you would do in Excel) it seems like repositioning grid after updating database would take some time with 15,000 record data table.Those are my initial concerns. Next will be Inventory Transaction followed by Reporting.Tell me how the Big Boys do it!Lee |
|
|
|
|
|
I need a SQL Mentor