- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I would have to remote in to see what is going on. But did you compare database versions between server and client? They must be exact. Or maybe a repair install of RPE.
Feel free to email me with more details if need be.
Your getting a connection successful because your looking at the localhost. The server would be the network name of your server. And the password is case sensitive and is pcAmer1ca. (Note the number 1, not an i)
Sheldon, The data might really be gone. There are several reasons you might lose data with Filemaker 7 including the file being closed unexpectedly due to power failure, so the application doesn't close the file properly, or the Filemaker application unexpectedly quitting. However, the data might still be recoverable in this scenario. Under the File menu there is a recover command you can try that will create a new "Recovered" file from the current one. Additionally, I strongly recommend you start a daily incremental back up for your FileMaker database files. While corruption issue are rare, accidentally deleting a record, or information in a field, or purposeful sabotage by an unhappy employee is permanent without a backup. Additionally, a back up would provide a solution for recovering the data in the event client data disappears in the future.
I hope I've done a good job answering your question. I am a FileMaker 7 expert (and 8, 9, and 10 as well); if you have any additional questions I will do my best to answer them. If my answer was helpful for you I'd appreciate a 5 thumbs up rating, or a click on the yes this was helpful button. Thank you!
Most likely it isn't deleting, it just is hidden in the view you are looking at. In the top right corner of the inbox is the option to View unread only, click on that and change it to view all and you should be able to see the emails.
Perform following steps to recover sql server database:
Create a database with same size that you are trying to recover
Shutdown the SQL server
Swap old mdf file with new mdf file
Start the SQL server
Database may go in suspect
Set database in emergency mode
Run DBCC CHECKDB with repair_allow_data_loss to repair database
USE [master] GO ALTER DATABASE [RdmStoreInformation] SET EMERGENCY GO ALTER DATABASE [RdmStoreInformation] SET SINGLE_USER GO DBCC CHECKDB ([RdmStoreInformation], REPAIR_ALLOW_DATA_LOSS) GO ALTER DATABASE [RdmStoreInformation] SET MULTI_USER GO ALTER DATABASE [RdmStoreInformation] SET ONLINE
We give below a brief note on TallySynchronization and Data Migration Process:
Synchronization refers to the process of Tally data being replicated between two or more locations. This enables a branch office to send its data to the head office over the Internet or a private network. Tally provides complete control over the frequency of replication. If the user is connected on a leased line, he can choose to replicate after every entry. If the user is not connected on a leased line, he can post his updates at specific intervals.
Synchronization is both ways - i.e., all data from the client company goes to the server and all data from the server company gets copied to the client company. After the synchronization has been set up, replicating data between the locations is a single click activity. Tally connects to the server, finds out the status of the last transfer (if any) and exchanges the incremental data that was entered after the last transfer. Tally also takes care of creating all mast! ers required to save the transaction on the target machine.