Use INI files instead - like a "poor man's database". Here's the general idea:
 Code:
; these values are gathered from the machine
$MAC="00-11-22-33-44-55'
$PC='pcname'
$IP='ip.add.res.s'

; Create or Update this PCs record
$ = WriteProfileString('some\path\PCData.ini', $MAC, 'PC', $PC)
$ = WriteProfileString('some\path\PCData.ini', $MAC, 'IP', $PC)
$ = WriteProfileString('some\path\PCData.ini', $MAC, 'All', $IP + ',' + $PC + ',' + $Mac)

; other code for your app...

; delete the record
$ = WriteProfileString('some\path\PCData.ini', $MAC)

This creates a file with one entry per pc that looks like this:

[00-11-22-33-44-55]
PC=SomePC
IP=ip.add.res.s
DATA=ip.add.res.s,SomePC,00-11-22-33-44-55

The last field could be the only field with few changes to your code, or you could eliminate it and change your code to read individual fields. There are UDFs to return a list of all records in the file, so you won't have to read the file line by line.

Writing an empty value deletes the record (and writing an empty value deletes the field). Using the MAC address as the record ID means that if a PC gets a new address from DHCP, it updates the same record with new data. Same deal if you rebuild/rename the PC - the MAC address doesn't change.

Look for the EnumINI UDFs here, and read about the ReadProfileString/WriteProfileString functions in the manual for more info.

Glenn
_________________________
Actually I am a Rocket Scientist! \:D