make table query corrupts hyperlink field

  • Thread starter Thread starter mcnews
  • Start date Start date
M

mcnews

has anyone had this problem? i have a make table query that selects
several fields including a hyperlink field into a new table. this has
been working for a couple of years. recently the new table's
hyperlink fields all contain junk characters. even the ones that
should be empty.
tia,
mcnewsxp
 
has anyone had this problem? i have a make table query that selects
several fields including a hyperlink field into a new table. this has
been working for a couple of years. recently the new table's
hyperlink fields all contain junk characters. even the ones that
should be empty.
Click to expand...

I don't know why this problem is happening, but I recommend not using
MakeTable anyway. It's actually more reliable to have a permanent
table, then delete all the records and reload it with an Append query
instead. Then you get a consistent structure with less opportunity
for Access to misinterpret the field types needed.

If you try it with an Append query into an existing table, does the
problem still occur?

Armen Stein
Microsoft Access MVP
www.JStreetTech.com
 
mcnews,

You never stated how big your database is or what version. I would also
make sure Name AutoCorrect is off, just because...

I also wonder why you don't create a query and use those results?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
 
i use 2007, but users are using 2003. i use 2003 at home.
i will try the append query idea.
 
append query does exactly the same thing
googling tells me that you can't group by hyperlinks.
wonder why it worked before and still works on older versions of the MDB?
 
Still curious...  how big is your database and when was the last time you
ran Compact and Repair?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
Click to expand...

we compact and repair regularly.
the make table query involves one table with around 8100 rows and
another with around 11000.
i created a test mdb that contains the 2 tables and the make table
query. i also imported the two tables from a previous version in
which the make table query was working properly. i discovered that
the corruption only occurs when one of the new tables is involved.
and if i delete rows from that table and make it contain the same
number of rows as the older one no corruption occurs. so there's some
bad data somewhere or something. i am going to experiment with
removing fewer and fewer rows to see where the breaking point is.
 
Do you get and Paster Errors table that might help you pin point what in
those rows of data is causing the problem?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Still curious... how big is your database and when was the last time you
ran Compact and Repair?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
Click to expand...

the new table has 8513 rows and the old has 8380. when i remove 133
records from the new table (first 133 or last 133) no corruption
occurs.
 
Do you get and Paster Errors table that might help you pin point what in
those rows of data is causing the problem?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm





the new table has 8513 rows and the old has 8380.  when i remove 133
records from the new table (first 133 or last 133) no corruption
occurs.
Click to expand...

no error message. again, i get no corruption when i remove 133 rows
from the top of the table or bottom of the table so i think i can
assume it's not something in the data that is causing the problem.
the reason for removing 133 rows is i get no corruption when using an
older version of the table that has 8380 rows.
 
McNews,

I realize the table that you remove the rows from gets no corruption once
you remove the rows HOWEVER since the additional rows are not a problem for
Access (I have brought in over 300,000 rows of data) I must assume that it
is the data. And for that reason I would want to either review the
PasteErrors table OR review the data itself, line by line, to figure out
what is the issue. Of course, you did say that it doesn't matter where you
remove the 133 rows of data from... very odd.

Also, looking back over your postings, I did not notice that you state the
overall size of your database. Using Make Table Queries does cause bloating
which COULD cause the symptoms your seeing.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

Do you get and Paster Errors table that might help you pin point what in
those rows of data is causing the problem?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm





the new table has 8513 rows and the old has 8380. when i remove 133
records from the new table (first 133 or last 133) no corruption
occurs.
Click to expand...

no error message. again, i get no corruption when i remove 133 rows
from the top of the table or bottom of the table so i think i can
assume it's not something in the data that is causing the problem.
the reason for removing 133 rows is i get no corruption when using an
older version of the table that has 8380 rows.
 
McNews,

I realize the table that you remove the rows from gets no corruption once
you remove the rows HOWEVER since the additional rows are not a problem for
Access (I have brought in over 300,000 rows of data) I must assume that it
is the data.  And for that reason I would want to either review the
PasteErrors table OR review the data itself, line by line, to figure out
what is the issue.  Of course, you did say that it doesn't matter whereyou
remove the 133 rows of data from...  very odd.

Also, looking back over your postings, I did not notice that you state the
overall size of your database.  Using Make Table Queries does cause bloating
which COULD cause the symptoms your seeing.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm






no error message.  again, i get no corruption when i remove 133 rows
from the top of the table or bottom of the table so i think i can
assume it's not something in the data that is causing the problem.
the reason for removing 133 rows is i get no corruption when using an
older version of the table that has 8380 rows.
Click to expand...

my test mdb that only has the 4 tables i need and a couple of version
of the make table query is 13,220 kb.
 
Okay I am getting stumped. I just ran a Make Table Query on a table with
13,000+ records and they all went thru just fine. Can you copy/paste the
SQL of your query?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

McNews,

I realize the table that you remove the rows from gets no corruption once
you remove the rows HOWEVER since the additional rows are not a problem
for
Access (I have brought in over 300,000 rows of data) I must assume that it
is the data. And for that reason I would want to either review the
PasteErrors table OR review the data itself, line by line, to figure out
what is the issue. Of course, you did say that it doesn't matter where you
remove the 133 rows of data from... very odd.

Also, looking back over your postings, I did not notice that you state the
overall size of your database. Using Make Table Queries does cause
bloating
which COULD cause the symptoms your seeing.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm






no error message. again, i get no corruption when i remove 133 rows
from the top of the table or bottom of the table so i think i can
assume it's not something in the data that is causing the problem.
the reason for removing 133 rows is i get no corruption when using an
older version of the table that has 8380 rows.
Click to expand...

my test mdb that only has the 4 tables i need and a couple of version
of the make table query is 13,220 kb.
 
Back
Top