sychron put "~sq_c" in front of and after the names of queries

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After sychronization I noticed that there is a whole list of queries
with"~sq_c" in front of and after the names of queries along with "combo(and
a number or the name of a combo if used)". Should I worry about this? I
have never had this happen before. What caused it now? I have been
synchronizing these replicas for a couple of months now. I did compress /
repair the database yesterday because I had a problem with an error when I
tried to update a table while a form that uses it was open. Can I expect
other problems to arise out of this?

Please help...I am new to replication but have used Access for 7 years.

Thanks.
 
I'm assuming that you have SQL specified as the Row Source for your
comboboxes and/or the Record Source for your forms, rather than specifying
the name of a query.

When you do that, Access actually creates a query using that naming
convention.
 
Douglas,

I used the wizard to create the combo boxes. The row source property has
the following code:

SELECT [N SUPPLIER TABLE LONG].[SuP Code], [N SUPPLIER TABLE LONG].[SuPplier
Description]
FROM [N SUPPLIER TABLE LONG]
ORDER BY [N SUPPLIER TABLE LONG].[SuPplier Description];

I don't think it has anything to do with this code, as I have had no
problems until now.

I think I have corrupted the database, when I tried to change a record on a
table (while a form that accesses that table was open...big mistake) I got an
error message telling me that the record had been changed by another user at
the same time...I then compacted and repaired the database and created
another replica and syncronized again.

I'm not sure I understand this statement: "When you do that (which? Use
SQL?Specify name of query?), Access actually creates a query using that
(which? SQL?Specify name of query?) naming convention." ?SQL naming
convention?

I read another thread from another member of the community with the same
thing - someone suggested that he split the database into a front-end (fe)
and back-end (be) structure...he had success with this but I am waiting for a
response as to how he accommplished this exactly.

Thanks for your response, its appreciated...most of this database works fine
the forms combo boxes etc...but I did get an error that I didn't have
permission to access a table that was used by one of my updates when testing
this out...I created the table with a new name and changed the update to
reference that table...
I am completely baffled about all of these strange issues and don't know
what to expect next. Should I revert to the backup and tell the user to
re-enter everything from yesterday and today?
 
I meant when you have SQL statements (rather than the name of a query),
Access will create the queries with the odd names.

Something does sound amiss, though, as those queries aren't normally shown
in the GUI (although you can see them if you list all of the queries using
code)

You definitely should split your application, though: the chances of
corruption are significantly higher if you've got multiple users sharing the
same database. Tony Toews has information about how to split at
http://www.granite.ab.ca/access/splitapp

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)



AccessAddict said:
Douglas,

I used the wizard to create the combo boxes. The row source property has
the following code:

SELECT [N SUPPLIER TABLE LONG].[SuP Code], [N SUPPLIER TABLE
LONG].[SuPplier
Description]
FROM [N SUPPLIER TABLE LONG]
ORDER BY [N SUPPLIER TABLE LONG].[SuPplier Description];

I don't think it has anything to do with this code, as I have had no
problems until now.

I think I have corrupted the database, when I tried to change a record on
a
table (while a form that accesses that table was open...big mistake) I got
an
error message telling me that the record had been changed by another user
at
the same time...I then compacted and repaired the database and created
another replica and syncronized again.

I'm not sure I understand this statement: "When you do that (which? Use
SQL?Specify name of query?), Access actually creates a query using that
(which? SQL?Specify name of query?) naming convention." ?SQL naming
convention?

I read another thread from another member of the community with the same
thing - someone suggested that he split the database into a front-end (fe)
and back-end (be) structure...he had success with this but I am waiting
for a
response as to how he accommplished this exactly.

Thanks for your response, its appreciated...most of this database works
fine
the forms combo boxes etc...but I did get an error that I didn't have
permission to access a table that was used by one of my updates when
testing
this out...I created the table with a new name and changed the update to
reference that table...
I am completely baffled about all of these strange issues and don't know
what to expect next. Should I revert to the backup and tell the user to
re-enter everything from yesterday and today?


Douglas J. Steele said:
I'm assuming that you have SQL specified as the Row Source for your
comboboxes and/or the Record Source for your forms, rather than
specifying
the name of a query.

When you do that, Access actually creates a query using that naming
convention.
Click to expand...
Click to expand...
 
Back
Top