I am building a tool that will create a dynamic load table that can be imported into a database, for legacy data conversion. The premise is that I can get the legacy data and map the appropriate fields for the CMMS application I implement. Then the tool checks which fields are present in the legacy table, matches the properties against my load table and replaces any differing fields with ones that have the correct properties. The theory behind this that I can just import the legacy data into my access DB with the correct configuration for the customer's database and I don't need to recode anything to load that data into their system. The only problem is that this CMMS package has certain required fields that most customers don't use, so I set default values into the load table so they will be populated with the appropriate default regardless of whether or not any information was provided by the customer.
The problem comes if I have a customer that does use that field and has a different configuration from the Out-of-the-Box CMMS package. If I cannot reset the default value in the modified field by code I will have to remember to do it by hand after I am done with that project, or use a virgin copy of my tool for every customer.
In DAO I found reference to a field object property called .DefaultValue, but I couldn't find anything equivalent in ADO or ADOX. Any help would be greately appreciated.
TIA,
Ian Nelson
The problem comes if I have a customer that does use that field and has a different configuration from the Out-of-the-Box CMMS package. If I cannot reset the default value in the modified field by code I will have to remember to do it by hand after I am done with that project, or use a virgin copy of my tool for every customer.
In DAO I found reference to a field object property called .DefaultValue, but I couldn't find anything equivalent in ADO or ADOX. Any help would be greately appreciated.
TIA,
Ian Nelson
