Member Avatar for abelingaw

SOFTWARE:
If i install a Payroll System made from VB6, would this be enough for its requirements..?


SOFTWARE:

Windows XP (Any Service Pack)
MS Access 2003 or Higher

HARDWARE:

Hardware Requirements

* 200 Mhz Processor
* 128 Mb RAM or Higher
* 100GB SATA (Serial Advanced Technology Attachment) Hard Drive
* 5400 RPM hard disk drive
* DirectX 9 capable video card running at 1024 x 768
* DVD-ROM Drive


Can u suggest any other/better specification (Windows XP SP3 / Windows 7)
Really dont know much about this Specs thingy..

Edited by abelingaw because: n/a
  • 3 Contributors
  • 2 Replies
  • 1K Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by PoisonedHeart

Dani AI

Generated

A short, practical summary for (and to expand on points from and ):

Visual Basic 6 programs themselves are small — the important parts are the VB6 runtime and whatever controls/DB drivers your project uses. Microsoft supports the VB6 runtime (not the IDE) on supported Windows versions (32-bit runtime runs under WOW64 on 64-bit Windows), so prefer a modern, supported OS rather than building around XP or Windows 7 (those have known end-of-support dates). (learn.microsoft.com)

Practical deployment checklist (keep an installer and a clean test VM that matches target OS/bitness):

  • Include the VB6 runtime and only the dependency files your app actually needs (min redist list + any OCXs). Use the Package & Deployment guidance or a modern installer and test on a clean VM. (ftp.zx.net.nz)
  • If the app uses Access files, bundle the matching Access runtime / Access Database Engine (ACE) or require the correct runtime be installed; match 32/64-bit. (microsoft.com)
  • For multiuser or larger datasets consider migrating the back end to SQL Server (Express) instead of a file-based Jet/ACE backend. (support.microsoft.com)
  • Document install steps (admin rights, ODBC DSNs, file permissions), include printer drivers and network/NIC requirements if you’ll run across LANs (as suggested), and test printing/reporting.

Quick troubleshooting tips: if you see “provider not registered” or OLEDB errors, install the correct Access Database Engine or change the provider string (Provider=Microsoft.ACE.OLEDB.12.0 vs Microsoft.Jet.OLEDB.4.0). If an OCX/DLL won’t load, register it with regsvr32 from an elevated prompt and check Event Viewer/UAC. Include all referenced components in your installer (as advised) and validate on the same OS/bitness you plan to support. (microsoft.com)

If more detail is wanted (example installer checklist, exact redist filenames, or a sample regsvr32 script for OCXs), those can be provided separately.

Recommended Answers

All 2 Replies

Member Avatar for kinwang2009

Abelingaw, I think that is enough for system requirement but make sure all reference components are included with your PayRoll System Installation package.
thanks

Member Avatar for PoisonedHeart

For me, since your Payroll system was made in VB6, then you could just use the system requirements(HARDWARE) of VB6.

Anyway, it also depends on your system, if your system is capable of, or requires to run in a client/server side, then you must include the necessary equipments to set up network computers(e.g. LAN card, utp cable RJ-45's and others)

any other hardware components that your system needed to run smoothly must be listed also, like printers etc...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.