I'm sorry. I was not clear enough.
The insert is occurring for the parent table Users.
The insert is bombing for the child table. And the frustrating part is that it is not consistently bombing.
It is saying that there is a conflict with the foreign key.
Thanks!
I am new to SQL Server so please bear with me.
I'm upgrading application from Access 2000 to SQL Server 7.0.
Is it possible in SQL to have child record automatically created when you insert into parent table using system
constraints rather than triggers?
Parent table ID is linked to child...
I have received the same error (Coinitialize has not been called) but not with consistency. I have found that when I log out and relogin that I can then add the tables. (This error happens in both creating views and diagrams)
I will pursue trying to reinstall EM to see if that clears it up.
I believe that Excel will only accept 65536 rows.
I've received error stating that as the limit.
I do not think you should have problem with 17000 rows.
I am not familar with FoxPro and any limitations it might have with the Copy To command.
Hope that helps.
Thanks!
Sorry for delay in responding. Between waiting for access to MS Access 2000 and getting redirected on another project, I finally was able to use your advice.
I am able to have users with different versions access the same database by the 2000 users using a different database linked to...
Thank you for your input.
Because the reports use information dynamically from the database I ended up using ASP to access the database and display the information using html.
Your post did give me an idea for another application though. Thanks!
I have an Access database with existing reports.
Is it possible to make this available through the web for
remote users to print their own reports?
What method would be used? HTML, ASP, JSP, or JavaScript? Or another altogether?
Thanks!
I have an Access 97 database on a network with majority 97 users and a handful of 2000 users. The handful are the test cases with intent of upgrading entire department eventually.
When a 2000 user opens database that is currently open by a 97 user it locks up the 2000 machine.
Staying...
MDE that is created prior to Access 2000 will not be able to be opened in Access 2000. The original database must be converted to Access 2000 and then a new MDE file recreated.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/off2000/html/achowMakeMDXFile.asp
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.