-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've never encountered a situation where I had to edit the schema.ini
file.
The import specification can be viewed using this kludgey method:
0. Open the .mdb file you want changed.
1. On the menu bar select File > Get External Data > Link Tables....
2. Select Text Files in the file type Combo Box on the file selection
dialog box.
3. Select any ole text file - it doesn't matter 'cuz we're going to
ignore the selected file. This is just to get to the Import
Specification wizard.
4. When the Link Text Wizard dialog box appears click the "Advanced"
button.
5. When the Link Specification dialog box appears click the
"Specs..." button.
6. The name of the spec that defines the text file/table should be
listed in the Import/Export Specifications dialog box. It will be
named something like "FileName Link Specification" where FileName is
the text file's name.
7. In the subform "Field Information" section change whatever needs
changing.
8. Save the specification under its original name (overwrite the old
spec).
9. Refresh the link using the Immediate (debug) Window like this
(type in & hit Enter):
currentdb.TableDefs("TableName").RefreshLink
Be sure to put in the correct "TableName."
I'm not sure this will "really" refresh the link, but it's worth a
try. Otherwise, you'll have to relink, after doing steps 0-9 (be sure
to use the modified Spec for the relink).
[Correct posting: There's probably a Microsoft newsgroup on tables or
db design.]
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBQB2VToechKqOuFEgEQJ9kQCdF6uz/vdTyNelH025sZBa7OYTuV0Anio6
rp8LV4xZBDivFX09+uWwAoaz
=fwYM
-----END PGP SIGNATURE-----
