import changes?

[martinwcole]

does anyone know of any changes in the way alpha handles imports?

I have a client where we import files regularly, sometimes twice or more a day.

It WAS working perfectly. It was "importing to an existing file."

On his, which is still running 1408 1035, it still works perfecly. But on mine, 1466 1044, it bombed. What I had to do to get it working on mine was "import to a new file" and then make the field types and lengths as needed and then append to the necessary files. Its working okay again.

Going back to 1408 1035 on mine didn't fix it - could be some changes were made to the registry as regards importing - doesn't make sense that it was working perfectly for months and then starts bombing.

What I also noticed is that if I made a new import to a new file - and then made the same import to an existing file (to the new file) it would not work - errors from the append engine

[Tom Cone Jr]

RE: import changes?

Martin,

the error messages might help if we could see them.

Check the release notes for list of changes and fixes. I don't recall anything that might affect what you're describing, although I'm confused whether you're importing or appending... (you say you're importing, but report errors with the 'append' engine).

I recommend you look for simpler explanations, like mismatched path statements.

-- tom

[martinwcole]

RE: import changes?

good point

well, am appending excel 4.0 tables to alpha dbf tables

when I use the prior method, namely importing to an existing file, i get the following error

script:template line 223
a_tbl.append()
variable append.m_exp1 references a non-existent field
@awsource_temp_table->ordernumber

the above message i'm pretty sure is more generic than specific, saying mainly that its unhappy with something in the defined import operation. [also, bear in mind that there are several import operations that WERE working that are no longer working - not just one]

i can make a new operation, importing to a new table, and i don't get error message. but if i then make another new operation, importing to an existing table, using the new table created in the first operation, i get the error message - so it seems related to the "import to an existing file", since in the above scenario, both dbfs are identical.

it was working since around January - just recently started bombing on mine - with a later build. he runs 2000 and i run xppro. It seems to be build related, but, even if i go back to an earlier build on mine its still there, so it would have to be someting written to the registry

but, since i found a fix, as described earlier, namely importing to a new table, and then appending to the table where i originally wanted it, i'm going to get him to install 1044 and see if the same thing happens on his. if it does then at least i can tie it to alpha - otherwise, i am totally baffled. we have identical directories, etc. i even had him fpt me his copy of his program and his copy of the excel files to test with, and to isolate against program/data differences between us.

[Tom Cone Jr]

RE: import changes?

Martin,

So, you're saying the 'import' operation created by the genie will fail every time you opt to import to 'an existing file' ???

-- tom