Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Back End Db tables not updated completely

Status
Not open for further replies.

crpjaviman

Technical User
Jan 24, 2002
57
US
Hello everyone,

Has anyone encountered the problem of the Back End db tables not being updated with the Front End db tables?

Here is an example of what I mean:

Front End table linked "Front" entry:
ID Name TimeArrived TimeLeft EntryTime
1234 Jane Doe 10:00 15:00 09:55

Back End Table "Front" entry shows:
ID Name TimeArrived TimeLeft EntryTime
"" "" "" "" 09:55

This has been happening for a few days, I have looked over the code and it works with the Front End. Is there some kind of delay in viewing the same records in the Back End?

Any suggestions?
Thanks,
crpjaviman [rockband]
 
Well, My first thought is to make sure that line level locking is in place...

Another thought I am having is the back end, is it access or some other system(oracle, sql...)

another thought is how are you updating your table, Is it through a bound table, or a query, or a recordset...

These are all just thoughts... I havn't had this or a similar problem so I'm just shooting in the dark with this...

Wish I could be of more help.

--James junior1544@jmjpc.net
Life is change. To deny change is to deny life.
 
Is the entry time coming from the first table or is it a default value being generated at the second table? If it is being generated at the table, it seems like none of the info is getting through whereas, if the time is coming from front end, it would indicate that some of the info isn't getting through. I know there are no reasons here, I have no idea what your problem could be. However, that info about the source of the time info might narrow it down for someone who does.
 
Let me try to shed some light and answer your questions:

junior1544,

Both of the sources are Access. The records are being saved via a recordset in the Front End. About the level locking, I don't quite understand the question, but if you are referring to the record locking, there are no locks.

JeremyNYC,

There should not be any difference between the two records, which is actually the same record. The first record is entered in the Front End which is linked to the Back End. The second entry is what is shown in the Back End table.

grnzbra,

The time is being generated in the Back End table.


If there is anyone that may have a solution, it would be much appreciated.

It is getting a little frustrating due to the amount of blank records that are being recorded.

Thanks,
crpjaviman [rockband]
 
crpjaviman,

OK, I think we are going to need a lot more information here to get you any help. Please describe your problem much more completely. What is happening. In your first post you mention that records don't match. In your second post you mention that you have a bunch of blank records. These are very different.

Where are you adding records? If it's in code, paste that code into a post. If it's with a query, paste the text in the sql view of the query.

Under what circumstances do you get extra records?

When you change an existing record, does that work correctly?

Jeremy =============
Jeremy Wallace
Designing, Developing, and Deploying Access databases since 1995.
 
jeremy,

The example is the same record. It is first saved into the table "Front" in the Front End db. It is supposed to update the Back End table of the same name when it is linked.

Basically, this is the way the tables should look like:

Front End table linked "Front" entry:
ID Name TimeArrived TimeLeft EntryTime
1234 Jane Doe 10:00 15:00 09:55

Back End Table "Front" entry should show:
ID Name TimeArrived TimeLeft EntryTime
1234 Jane Doe 10:00 15:00 09:55

Correct?

Well, the example on my first post does not reflect this, it reflects that the record in the Back End was not saved completely.

I really should apologize, I did not say in my first post that the example is not a correct representation for all of the records. Most of the records are being saved correctly and completely. There are no extra blank records. I have not been able to pin point which records do not save and the reasons.

As far as the code, I believe that if the record is being saved completely in the Front End, is should reflect completely in the Back End.

Am I wrong to think this way?
Thanks,
crpjaviman [rockband]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top