Downloads

Prep ISG Sheet

This shareware spreadsheet from Mike Clare (ddmsuderground guru) will read the FULLRDC spreadsheet that is published by IS.Group and create 3 additional columns The columns are called 'MyUOM', 'MyQty' & 'MyPrice'. The problem this sheet is attempting to solve is the result of the IS.Group spreadsheet not having a clear cut set of columns that can be used to give you accurate pricing under the two buying scenarios that you can use when buying from the RDC. The IS.Group sheet gives you info that will allow you to do pricing on either a full case or break case basis but you have to interpret it on a line by line basis. The program (macro) embedded in this sheet automates this process and builds the above columns based on whichever scenario you choose. Additionally, the little program can also read your DDMS master and manufacturer files to do a reality check to see how the items on the spreadsheet match up against your DDMS data. You can run the program before or after you do your C2 or OPUS load to compare the data in your DDMS system to the spreadsheet published by IS.Group

Sub Sifter

This shareware spreadsheet from Mike Clare (ddmsunderground guru) reads the DDMS I-Master file and builds the chain of alternate items associated with the master item. If it finds a dead link (an alternate that does not exist) or a circular reference (an alternate that points back to a previous link in the chain) it flags them in the spreadsheet.You must set your macro security in Excel to Medium or Low in order to run the functions in this spreadsheet

Visual FoxPro ODBC Driver

This Web release of the Microsoft Visual FoxPro ODBC Driver is intended for customers who have installed Microsoft Data Access Components (MDAC) version 2.6 or higher. The Visual FoxPro ODBC Driver is included in MDAC 2.5, which is installed under System File Protection on the Microsoft Windows Millennium and Microsoft Windows 2000 operating systems. Customers running Windows Millennium and Windows 2000 should not install this driver. Additionally, if you have upgraded to MDAC 2.6 from MDAC 2.5, you do not need to install the Visual FoxPro ODBC Driver. You can find out whether you already have the Visual FoxPro ODBC Driver installed by checking to see if a file called VFPODBC.DLL exists in your Windows System directory.

Data Access Component 2.6 SP2

The MDAC 2.6 SP2 redistributable installer installs the same Data Access core components as Microsoft SQL Server 2000 SP2. This release does not include Microsoft Jet, the Microsoft Jet OLE DB Provider, the Desktop Database Drivers ODBC Driver, or the Visual FoxPro ODBC Driver.

Access Jet Database SP3

Jet40SP3_Comp.exe is a complete set of Jet 4.0 components for Microsoft Windows 95, Microsoft Windows 98, and Microsoft Windows NT version 4.0. Jet40SP3_Comp.exe gives you the complete Jet 4.0 components up to Service Pack 3 (SP3). This is the same version of Jet that ships with Microsoft Windows 2000 and Microsoft Windows Millennium Edition (Me).

Automatic Defragment Script

Use the enclosed script to schedule an automatic defrag of the drives on on computers running Windows 2K or XP. Just set a scheduled task in windows to run the script and it will defragment all of the drives on your computer.

ODBC Data Access Information

In the most basic kind of database design, applications rely on only one database. In such a simple setup, an application developer can program directly against the database system's interfaces. Although this approach provides a quick and efficient way to access data, it often poses a big problem when a business expands and the developer must scale up the application. The one-database approach also means that each off-the-shelf application must have a different version to support each database. As businesses change, grow, and merge, applications must access multiple databases running on different platforms. ODBC technology provides a common interface for accessing heterogeneous SQL databases. ODBC uses SQL as a standard for accessing data. Figure 1, page 30, shows a diagram of a standard ODBC architecture. This interface provides maximum interoperability: One application can access different SQL database management systems (DBMSs) through a common set of code. Thus, a developer can build and distribute a client/server application without targeting a specific DBMS. The developer can add database drivers to link the application to the user's choice of DBMS. As Figure 1 shows, the driver manager provides the intermediate link between the application and the databases. The ODBC interface contains a set of functions that the drivers of each DBMS implement. When an application changes its DBMS, the developer simply replaces the old driver with the new DBMS's driver and the application can work as usual—without the need for code modifications.